Transcription

CoRaSatCOgnitive RAdio for SATellite CommunicationsFP7-ICTCollaborative Project - Grant Agreement no.: 316779Collaborative projectDeliverable D4.2Test Plan DocumentProject acronym:Project full title:Grant agreement no:Project web site:CoRaSatCOgnitive RAdio for SATellite Communications316779www.ict-corasat.euDeliverable No.D4.2Delivery DateM30Work Package No.WP4Work Package Title:CoRaSatTestDemonstrationandAuthors (Partner) (per Beneficiary, if more Mostafa Pakparvar, Joel Grotz (Newtec)than one Beneficiary provide it together)Eva Lagunas, Symeon Chatzinotas, Sina Maleki, ShreeSharma (Uni Luxembourg)Barry Evans, Paul Thompson (Uni Surrey)Alessandro Guidotti, Daniele Tarchi, AlessandroVanelli-Coralli, Vincenzo Icolari, Giovanni E. Corazza,Carlo Caini (Uni Bologna)Status (F: final; D: draft; RD: revised draft): FDissemination level:PU(PU Public; PP Restricted to other programparticipants;RE Restricted to a group specified bytheconsortium;CO Confidential,onlyformembers of the consortium.NTCCoRaSat Del D4 2 r1 v0.docProject start date and duration01 October 2012, 36 month

INTENTIONALLY LEFT BLANKRelease 0.06 (Working draft)pag. 2 of 38

ICT 316779 CoRaSatDeliverable D4.2TABLEOFCONTENTS1EXECUTIVE SUMMARY . 52SCOPE AND STRUCTURE OF THE DOCUMENT . 63TEST PLATFORM INTERFACES AND PARAMETERS . 7453.1TEST PLATFORM - HARDWARE SETUP . 83.2PARAMETERS RECORDED DURING THE MEASUREMENTS . 93.2.1Configure Terminal Interface . 133.2.2Configure Channel Emulator Interface . 143.2.3Configure SatNet Configurations Interface . 15DEMONSTRATION USE CASES . 174.1SELECTED CONFIGURATION SCENARIO FOR SCENARIOS A AND B . 184.2SELECTED CONFIGURATION SCENARIO FOR SCENARIO C . 184.3TEST CONTROL INTERFACE OF THE COMBINED 8 TEST-CASES . 194.4CONFIGURATION . 204.5SCENARIOS A AND B EMULATION . 204.6SCENARIO C EMULATION . 21TEST PLAN . 235.1TEST CASE #1: INSTALLATION/DEPLOYMENT OF A NETWORK OF TERMINALS WITHIN A COGNITIVE ZONE 235.2TEST CASE #2: CHANGE NETWORK CONFIGURATION OF THE FSS TERMINAL IN THE PRESENCE OFINCUMBENT USER LINK INTERFERENCE . 235.3TEST CASE #3: MEASURE NETWORK EFFICIENCY WITH AND WITHOUT RA TECHNIQUE USAGE . 245.4TEST CASE #4: DETECT INTERFERENCE PRESENT FROM INCUMBENT USER ON THE FORWARD LINK . 245.5TEST CASE #5: CHANGE THE FORWARD LINK CARRIER CAPACITY ALLOCATION ACCORDING TOINCUMBENT USER INTERFERENCE PRESENCE . 255.6TEST CASE #6: MEASURE THE INTERFERENCE LEVELS FROM CONFIGURED FSS SYSTEM ON THE RETURNLINK AT THE FS RECEIVER INPUT . 255.7TEST CASE #7: CHANGE THE RETURN LINK CARRIER FREQUENCY, POWER, RATE ACCORDING TOINCUMBENT USER . 255.8TEST CASE #8: (OPTIONAL) TEST ESOMP MOVEMENT THROUGH THE EMULATED ENVIRONMENT OF THEINCUMBENT INTERFERENCE . 266TEST PROCEDURE . 276.1TEST PROCEDURE #1 - INSTALLATION/DEPLOYMENT OF A NETWORK OF TERMINALS WITHIN A COGNITIVEZONE276.2TEST PROCEDURE #2 – CHANGE NETWORK CONFIGURATION OF FSS TERMINAL IN INCUMBENT USER LINKINTERFERENCE PRESENCE . 286.3TEST PROCEDURE #3 – MEASURE NETWORK EFFICIENCY WITH AND WITHOUT RA TECHNIQUE . 286.4TEST PROCEDURE #4 - DETECT INTERFERENCE PRESENT FROM INCUMBENT USER ON THE FORWARD LINK296.5TEST PROCEDURE #5 - CHANGE THE FORWARD LINK CARRIER CAPACITY ALLOCATION ACCORDING TOINCUMBENT USER INTERFERENCE PRESENCE . 296.6TEST PROCEDURE #6 - MEASURE THE INTERFERENCE LEVELS FROM CONFIGURED FSS SYSTEM ON THERETURN LINK AT THE FS RECEIVER INPUT . 30Release 0.06 (Working draft)pag. 3 of 38

ICT 316779 CoRaSat6.7Deliverable D4.2TEST PROCEDURE #7 - CHANGE THE RETURN LINK CARRIER FREQUENCY, POWER, RATE ACCORDING TOINCUMBENT USER . 306.8TEST PROCEDURE #8 - (OPTIONAL) TEST ESOMP MOVEMENT THROUGH THE EMULATED ENVIRONMENTOF THE INCUMBENT INTERFERENCE . 317CONCLUSIONS AND NEXT STEPS . 328DEFINITION, SYMBOLS AND ABBREVIATIONS . 339DOCUMENT HISTORY . 3510APPENDIX: TEST SETUP CALIBRATION . 3610.1METHODOLOGY . 3610.2EXAMPLE . 38Release 0.06 (Working draft)pag. 4 of 38

ICT 316779 CoRaSat1Deliverable D4.2EXECUTIVE SUMMARYThe aim of WP4 is the demonstration and validation of the CoRaSat concept through testbedimplementation of the selected scenarios in a laboratory environment. This deliverable, namely D4.2“Test Plan Document,” aims at providing a detailed description of the tests executed in the contextof this project, as well as the test procedures. These tests are executed on the demonstration platformdefined on the basis of the storyboards provided in D4.1 and the test platform reported in D4.3.Therefore, this deliverable shall be considered along with D4.1 and D4.3, as, together, they providethe overall context in which the scenarios identified in the CoRaSat project will be demonstrated.For this purpose, we follow the set of defined storyboard cases provided in D4.1 and define all of therequired input and output parameters for the test platform.The defined procedures serve as basis for the formal testing, which is subsequently reported in D4.5,“Formal Test Demonstration”. This is then used to test the defined cognitive techniques as proposedwithin WP3 and as adapted to the demonstration platform within WP4.The overall testplan is then executed and the results of the executed tests in this document are reportedin D4.4 “Integration and Testing” document, as well as the D4.5 formal test document.Release 0.06 (Working draft)pag. 5 of 38

ICT 316779 CoRaSat2SCOPEANDDeliverable D4.2STRUCTUREOF THEDOCUMENTThis document describes and details the test plan of the demonstration setup platform of the CoRaSatdemonstrator. The storyboard has been defined in document D4.1 and this document further outlinesthe tests to be executed, following the defined use cases of the storyboard document. In particular, theincumbent and cognitive system representations are provided, together with the channel emulator thatincludes incumbent, cognitive, and interference channels. Moreover, the interference detection by thecognitive channel and the network response is considered.A subsequent test procedure (detailed execution plan) is defined as a consequence of this testplan.In this deliverable, the key performance indicators and metrics defined in the CoRaSat context arelinked to the measured values in the laboratory setup.The document is organized as follows.In Chapter 3, the input and output parameters are defined and their usage on the current test platformis described together with the resulting measurement points exploited to verify the test outcome.In Chapter 4, the use cases are summarized and the end-to-end test scenarios are explained. These arebased on D4.1, which contains 8 scenarios that are outlined in more details and in a step-by-step testapproach, explaining all intermediate steps for the tests.In Chapter 5, the detailed test plan is outlined in a step-by-step manner: the tests are described withinput and output parameters, and the relation to the key performance indicators is provided.Chapter 6 outlines the test procedure and the instrumentation parameters are defined for each test case.In Chapter 7, the outline of the following work is described and the conditions of the testing as well asexpected outcome are depicted.Release 0.06 (Working draft)pag. 6 of 38

ICT 316779 CoRaSat3Deliverable D4.2TEST PLATFORM INTERFACESANDPARAMETERSThe test setup details are described in D4.3. All of the sub-components and hardware used in the testsetup are defined in this document. In the following, the resulting input/output parameters by the testequipment and the measurement points are defined.The test platform provides, for each test case, the following interfaces and measurement points, whichare read and configured by the test control PC.The overall parameters from the equipment in the test-plan are listed in Table 1, while Figure 1illustrates the CoRaSat demonstration test setup elements.Table 1 - Emulation of the CoRaSat setup elements used for the tests.Terminal 1-8Channel EmulatorGateway EmulatorDatabase EmulatorST-01 to ST-08CHeGWeDBeTerminal locationsConfigured linkConfigure 8 terminalConfigure the(latitude, longitudeattenuation for 8 returnrates forward and returnsurrounding interferenceelevation)linkslinkof incumbent users forTraffic Allocation FWDConfigure SNR levels forand RTN linkthe 8 return linkAllocate 8 terminals toConfigure InterferenceFWD1 / FWD2levels for the 8 returnAllocate 8 terminals toscenarios A, B and C.linkscarriers on return linkRTN1 / RTN2Figure 1 - Illustration of the CoRaSat demonstration test setup elements.Release 0.06 (Working draft)pag. 7 of 38

ICT 316779 CoRaSatDeliverable D4.23.1 Test Platform - Hardware SetupThe hardware setup consists two racks of equipment, which include the elements in Table 2.Table 2 - List of hardware setup test platform equipment.EquipmentChannel Emulator 8 portProgrammable and configurableTerminals MDM3300 with standard software(no modifications)IP Switch/Router 24 portsChannel control PC/serverWith specific software to control the emulatorNumber of unitsRemarkSpecifically setup for the CoRaSat test3setup to emulate signal, interference onthe forward and return for 8 andard switches with no specificchanges.Dedicated control PC with specific1CoRaSat software to control the 8channel emulator attenuator settings.Specific traffic server for this setup.Traffic test server2Standardserverequipmentwithdedicated specific configuration andsoftware.Hub demodulators MCD60002Hub controller serverServer group for all hub related controller1softwareOne on each SatNet(one per carrier group)Standard product equipment with nospecial changes for the setup.Dedicated CoRaSat control PC withCoRaSat control PCRunning specific software for User Interfacecontrol software, user interface and1emulation of the devised cognitivetechniques, including DB, RA, SS-and CoRaSat controller emulatorSNIR techniques.Dedicated, specific server running anDatabase server emulator1SQL database with data from UNIS forthe selected geographic area.Hub modulator for forward linksHub edge router for traffic and managementand control trafficFS link emulator(MDM6000 equipment with standard software)Release 0.06 (Working draft)2Standard equipment for the forwardlink transmission.Standard equipment for the IP data and1controlplaneroutingandtraffichandling.Standard equipment with no special1changes used to emulate the transmitinterference levels.pag. 8 of 38

ICT 316779 CoRaSatDeliverable D4.2Specifically developed satellite channelemulator (running on an MDM6000Satellite channel emulator2For satellite link emulationhardware with specific Add-on board).Emulates delay and satellite nonlinearity and filtering.Spectrum Analyzer for FS link receiver1emulationSplitters, combiners, noise source injection andspecific cabling and setup for forward and1return link L-band connectivityRacks for equipment housing2Standard spectrum analyzer equipmentconnected to the test setup.Standard cabling and signal routingequipment.Standard rack equipment.3.2 Parameters recorded during the measurementsThe following lists all the data recorded during the lab testing. Specific intermediate and final resultsare computed, which is also mentioned explicitly in Table 3.Table 3 - List of link parameters for the CoRaSat test platform control and monitoring.ParameterTypeDescriptionReturn link parametersThe C/N is a measured value at theC/N [dB]Return link measured C/N at thedemodulator input to the hub. Thedemodulator input.measurement is collected by theCoRaSat control server.RxLevel [dBm]Receive level at the demodulatorinput.The receive level is measured at thehub demodulator input and collectedby the CoRaSat control server.The central frequency for each returnlink carrier is configured by theCentral Frequency [MHz]Center frequency of all return linkHRC/MxDMAcarriers of the 8 terminals in MHz.CoRaSat) and is read by the CoRaSatThe emulated uplink RF frequency isserver for information and trackingshown.only. No specific configuration iscontroller(notperformed: this is done by theHRC/MxDMA server only.Errored SecondsBit Rate [bps]Release 0.06 (Working draft)Counter on the return link side thatCount of errored seconds, resultingindicates decoding errors occurringfrom CRC checks in the demodulatoron a per-second count basis.at the hub input.Return link channel bitrate for eachThe bitrate indicates the instantaneousof the logged On 8 terminals.channel bitrate and canpag. 9 of 38

ICT 316779 CoRaSatDeliverable D4.2The transmit power on the return linkis centrally controlled by the hub,Tx Power [dBm]Transmit power of the terminals forwhicheach of the 8 terminals.interference into a known FS rterminal for the scenario C case.Modulation and coding used for eachterminal. This is an index covering allmodulation and coding scales fromMODCODQPSK, 8PSK, 16APSK and 32APSK.A total of 45 different MODCODsettings covering the EsN0 rangefrom-0.6dBto16dBwithefficiencies from 0.7 to 4.5 bps/Hz.The modulation and coding settingsare managed centrally by the adaptivecoding and modulation (ACM) of thetwo-way system. This is working “inthebackground”andwaswellimplemented and tested already priorto the CoRaSat project.This parameter changes with theSymbol Rate [baud]Current symbol rate of the carrier ofthe considered return link carrier.automatedreturnlinkbandwidthmanagement to fit the need of thetraffic transmitted over the link of thatterminal.EfficiencyEfficiency recorded for the terminalThe efficiency indication is based onon the return link, given the currenttheMODCOD settings in [bps/Hz].terminal.currentModCodusageperThis throughput value indicates thecurrent throughput and can changeThroughput [Mbps]Current return link throughput inMbps.according to the centrally decidedallocation of power, bandwidth andmodulation and coding settings perterminal. This follows the Newtec“MxDMA.”Forward link parametersSatNetIndicates the satellite network usedConfiguration/control of the Satnet inSatNet-1the CoRaSat controller, which is then(FWD1)orSatNet-2(FWD2).configured and set on the platform.The forward link frequency is pre-FrequencyEmulated RF receive frequency ofconfigured for each SatNet (SN-1 andthe used SatNet.SN-2) and is then read and switchedby the CoRaSat control server.Signal to noise and interference ratioC/(N I) [dB]measuredonthereceptionat theterminal.TheforwardlinkThis is the measurement basis that isinput toeachusedmeasurementiscollected by the CoRaSat controlforthespectrumsensingcomputations as described in D3.4and D4.3server.Release 0.06 (Working draft)pag. 10 of 38

ICT 316779 CoRaSatDeliverable D4.2Expected C/N level at the input toC/N .exp [dB]each terminal based on link budgetThis value is used in the SS-SNIRcalculationsmethod as outlined D3.4 and N I).lta [dB](movinglongaverageoverseveralseconds) with the value for theC/(N I) measured.Receive level measured in the inputforRxLevel [dBm]theeightterminals.Themeasurement on each terminal inputis collected by the CoRaSat controlserver.Long-term average of the receiveRxLevel.lta [dBm]level. The LTA is computed in theCoRaSat control server.This value is taken into account in theSS-SNIR method as described D3.4and D4.3This value is used to measure theinput receive level and is used in theSS-SNIR method as described D3.4and D4.3Long-term average of the receivelevel used in the SS-SNIR method asdefined in the SS-SNIR methoddescription in D3.4 and D4.3.The ModCod settings on the forwardModCodIndex of the modulation and codinglink are set by the ACM mechanismused in the forward link (based onof the forward link. This is running inDVB-S2 MODCODs), ranging over“background” in the context of thethe QPSK, 8PSK, 16APSK, 32APSKCoRaSat demo setup and keeps therange.links up even under varying and lowSNRs.The mean efficiency is used toMean Efficiency [bps/Hz]Efficiency of the forward link inmeasure the forward link capacity of[bps/Hz] for the range considered.the setup and is used as metric of thesystem capacity.The symbol rate on the forward link isconfigured in the forward link system.Symbol Rate [Kbaud]Configuration of the forward linkThis is a basic setting, and is takensymbol rate in Kbaud.into account by the CoRaSat controlserver as occupied bandwidth only forthe interference assessment.The database assessed interferenceC/I DB [dB]Expected (computed) C/I value fromimpact is used to configure thethe database value measurement ofterminals to either forward linkthe interference level and combined(SatNet-1 or SatNet-2). The overallwith the link budget value for theimpact of all terrestrial interference issignal.taken into account. The CoRaSatcontrol server computes these values.Release 0.06 (Working draft)pag. 11 of 38

ICT 316779 CoRaSatC/I SS [dB]Deliverable D4.2Signal to interference ratio resultingThe C/I estimate is based on thefrom the spectrum sensing with thecomputationusage of the C/(N I) measurement atC/(N I) measurement value and thethe terminal input and the comparisonlink budget estimates of the C/N.expto the link budget expected value.value.ComputedInterference[dBW/ BW in MHz]interferencelevelresultingfromtheasThis interference level is the basis forresulting from reading the databasethe computation of the database basedand as computed by integration of allC/I DB value, which is subsequentlyinterference contributions over theused to control the channel settingscarrier bandwidth.for the emulation of the link.The forward link throughput perMeasured throughput of the forwardThroughputlink “iperf” process that is running atIP level to verify the link connectivityand performance.terminal is assessed on the basis ofthe end-to-end IP traffic passingthrough the link and this is measuredon the connected traffic test serverson either side (behind the terminaland behind the hub).All these control and monitoring parameters are managed and controlled through a centralized userinterface for the CoRaSat setup specifically.Figure 2 illustrates the user interface for this setup. Three panels that access the terminalconfiguration, the channel configuration, or the SatNet configuration are present. The geographiccontext is also illustrated on Figure 2.The selection of the forward link channel over the simulated detailed area is selectable and configuredover the link.Release 0.06 (Working draft)pag. 12 of 38

ICT 316779 CoRaSatDeliverable D4.2Figure 2 - User interface for the test platform control and monitoring.3.2.1 Configure Terminal InterfaceThe terminal configuration foresees to define all provisioned terminal parameters such as thosereported in Table 4.Table 4 - Terminal configuration.Terminal parameterComment / UnitLatitudeFSS Earth station emulated latitude in degrees NorthLongitudeFSS Earth station emulated longitude in degrees EastEnable IP traffic from traffic server (connected to the hub) toIperf traffic forward linktraffic client (behind the modem)10Mbps IP UDP traffic configured in Best Effort modeRelease 0.06 (Working draft)pag. 13 of 38

ICT 316779 CoRaSatDeliverable D4.2Enable IP traffic from traffic server (connected to the modem) totraffic client (behind the hub)Iperf traffic return link4Mbps IP UDP traffic configured in Best Effort modeActivate Resource Allocation on theSelect RA activation or notforward linkSatNet selectionSelection between SatNet-1 and SatNet-23.2.2 Configure Channel Emulator InterfaceThe channel emulator is configured as shown in Table 5.Table 5 - Terminal configuration.Channel parameter settingDescriptionCustom attenuation levelFWD SignalManually configured signal attenuation setting for the forwardlink signal levels of the 8 terminal links emulatedFWD InterferenceManually configured interference attenuator setting for theforward link interference of the 8 terminal links emulatedRTN SignalManually configured return link attenuator setting for the FSinterference input emulationCustom traceA configuration in terms of samples for a pre-defined fading event can be applied.The samples are copy/pasted in the “custom trace” interface window in the defined format as a text with onesample per line, time stamp in [sec] and signal attenuation level in [dB].Predefined eventsThe pre-defined events option allows to specifically attenuating the signal or the interference level of onespecific terminal.A pre-defined fading event is applied in this case, as shown in Figure 3.Release 0.06 (Working draft)pag. 14 of 38

ICT 316779 CoRaSatDeliverable D4.2Figure 3 - Heavy rainfade time series example.3.2.3 Configure SatNet Configurations InterfaceThe SatNet configuration interface foresees the configuration of the forward link satellite networkconfiguration for each of the 8 terminals in the emulation network.A specific forward link frequency is selected. A pre-defined 30Mbaud link is applied for the forwardlink. The following table summarizes the emulated center frequencies.Table 6 - Forward link emulated carriers’ center frequencies.Release 0.06 (Working draft)Carrier numberRF center frequency 6.5718109.5818172.5918235.51018298.51118361.5pag. 15 of 38

ICT 316779 CoRaSatDeliverable 718739.51818802.51918865.52018928.5Exclusive band option2119.7-20.2 GHzNo FS interferenceEach of the SatNet configurations can be configured to either of these settings to emulate differentcontexts.The configuration then emulates the environment for the defined geographical area and theinterference context for that carrier at the defined terminal location.The interference context is illustrated on the user interface and each terminal interference level isindicated on the interface as well.Release 0.06 (Working draft)pag. 16 of 38

ICT 316779 CoRaSat4Deliverable D4.2DEMONSTRATION USE CASESThe use cases are defined in D4.1 and, in the following, we review the use cases in more details. Theimpact on the different elements of the test platform is also taken into account.Table 7 - Considered test cases following the storyboard defined.Use caseDescriptionConfiguration tion test.andTest procedure usedRTNandofFWDlinkTest procedure yment of a networkof terminals within a cognitive zone.environment for scenariointerference presence.A / B.Measure network efficiency with andwithout RA technique usage.incumbent user on the forward link.allocationincumbentaccordinguserenvironment for scenariotointerferenceSelectedenvironment for scenarioSelectedConfigurationenvironment for scenariolink at the FS receiver input.C.carrierSelectedConfigurationenvironment for scenarioincumbent user.C.TESTTest ESOMP movement through theemulatedenvironmentincumbent interference.Release 0.06 (Working draft)oftheSelectedTest procedure #6Configurationfrequency, power, rate according toESOMPTest procedure #5A / B.environment for scenariolinkTest procedure #4A / B.configured FSS system on the returnreturnTest procedure #3ConfigurationSelectedtheTest procedure #2ConfigurationMeasure the interference levels fromOPTIONAL:8SelectedConfigurationA / B.Detect interference present fromcapacityTest procedure #1A / B.FSS terminal in incumbent user linkChange7environment for scenarioSelectedpresence.6ConfigurationChange network configuration ofChange the forward link carrier5SelectedTest procedure #7Configurationenvironment for scenarioTest procedure #8A / B & C.pag. 17 of 38

ICT 316779 CoRaSatDeliverable D4.24.1 Selected configuration scenario for scenarios A and BA geographical area with BSS feeder links and FS link presence is emulated in the [17.3-19.7] GHzband using geographic and interference data from the same area.Figure 4 - Emulated interference context for the scenario A and B. The 8 FSS terminals are assumed in thecontext of a real computed FS link interference computed for scenario B [17.7-19.7GHz] for a definedgeographic location.The assumed area in this case is the greater London area in the UK, which is relatively dense in termsof FS links and therefore represents an interesting geographic context to emulate. The emulation gridprecision was chosen to be 1km x 1km in this context.The channels within the forward link contexts to be emulated can be selected so that a definedinterference context is emulated, which is of relevance for the cases to study.Figure 5 - Illustration of the signal and interference computation for the emulated terminal locations.4.2 Selected configuration scenario for scenario CA geographical area with an FS link presence is emulated in the [27.5-29.5] GHz band. The FSreceiver location is defined, as well as the terminals transmitting on the return link.The overall link between the terminals and the FS receiver station is then computed and emulated.Release 0.06 (Working draft)pag. 18 of 38

ICT 316779 CoRaSatDeliverable D4.2The 8 return link interferences of the terminals in the potential vicinity of the FS link receiver areemulated via the interference links Interf 1 to Interf 8 and combined at the assumed location of the FSlink receiver in a spectrum analyzer representing the FS link receiver input.Figure 6 - Emulated context for the scenario C with N 8 terminals.4.3 Test Control Interface of the combined 8 test-casesThe Graphical User Interface (GUI) concisely integrates all the functionalities stipulated in D 4.1 intoa window with separate views for terminal configuration and channel emulation.Figure 7 - CoRaSat demonstrator main window, which is used for the execution of the presented test plan.Release 0.06 (Working draft)pag. 19 of 38

ICT 316779 CoRaSatDeliverable D4.24.4 ConfigurationThe 8 terminals are emulating a position within a defined geographic context. Two SatNets (differentforward links) are configured to connect the terminals to the platform with in addition the returncarrier group (RCG) configured such that.The following figure illustrates the configuration of the two used SatNets as well as the emulatedfrequency plan. The principle is that two separate forward and return link carriers and carrier groupsare used to emulate the two-way end-to-end service. The overall system is allocating the individualterminals to either the forward carrier FWD1 or FWD2, depending on its assignment for the overalllink.The control and management is centralized in the CoRaSat control PC emulation th

Satellite channel emulator For satellite link emulation 2 Specifically developed satellite channel emulator (running on an MDM6000 hardware with specific Add-on board). Emulates delay and satellite non-linearity and filtering. Spectrum Analyzer for FS link receiver emulation 1 Standard spectrum analyzer equipment connected to the test setup.