deliverable d4.5 formal test demonstration · release 0.01 (final draft) pag. 7 of 24 4 test cases...

CoRaSat

COgnitiveRAdioforSATelliteCommunications

FP7-ICT

CollaborativeProject-GrantAgreementno.:316779

Collaborativeproject

DeliverableD4.5FormalTestDemonstration

Projectacronym: CoRaSatProjectfulltitle: COgnitiveRAdioforSATelliteCommunicationsGrantagreementno: 316779Projectwebsite: www.ict-corasat.eu

DeliverableNo. D4.5

DeliveryDate M36

WorkPackageNo. WP4 WorkPackageTitle: CoRaSat Test andDemonstration

Authors(Partner)(perBeneficiary,ifmorethanoneBeneficiaryprovideittogether)

JoelGrotz,MostafaPakparvar(Newtec)

EvaLagunas,SymeonChatzinotas,SinaMaleki,ShreeSharma(UniversityofLuxembourg)

BarryEvans,PaulThompson(UniversityofSurrey)

AlessandroGuidotti,DanieleTarchi,AlessandroVanelli-Coralli,VincenzoIcolari,GiovanniE.Corazza,CarloCaini(UniversityofBologna)

Status(F:final;D:draft;RD:reviseddraft): F

Disseminationlevel:

(PU = Public; PP = Restricted to other program

participants;RE=Restrictedtoagroupspecifiedby

the consortium;CO = Confidential, only for

membersoftheconsortium.

PU

NTC CoRaSat_Del_D4_5_r1_v0.doc

Projectstartdateandduration 01October2012,36month

Release0.01(Workingdraft) pag.2of24

INTENTIONALLY LEFT BLANK

ICT−316779CoRaSat DeliverableD4.5

Release0.01(finaldraft) pag.3of24

TA B L E O F CO N T E N T S 1 EXECUTIVE SUMMARY ............................................................................................................................. 4

2 SCOPE AND STRUCTURE OF THE DOCUMENT .................................................................................. 5

3 TEST PROCEDURE REVIEW ..................................................................................................................... 6

4 TEST CASES RESULTS RECORDS ............................................................................................................ 7

4.1 TEST RESULTS – USE CASE #1 ..................................................................................................................... 74.2 TEST RESULTS – USE CASE #2 (SPECTRUM SENSING) ................................................................................ 114.3 TEST RESULTS – USE CASE #2 AND #5 (DB RECONFIGURATION) .............................................................. 124.4 TEST RESULTS – USE CASE #3 – MEASURE NETWORK EFFICIENCY WITHOUT AND WITH RESOURCE

ALLOCATION (RA) .............................................................................................................................................. 134.5 TEST RESULTS – USE CASE #4 AND # 6 ...................................................................................................... 144.6 TEST RESULTS – USE CASE #7 – CHANGE THE RETURN LINK CARRIER FREQUENCY, POWER AND RATES

ACCORDING TO INCUMBENT USER ENVIRONMENT ............................................................................................... 164.7 TEST RESULTS – USE CASE #8 – ESOMP MOVEMENT EMULATION THROUGH COVERAGE AREA ............... 17

5 RESULTING PERFORMANCE INDICATORS ....................................................................................... 18

6 CONCLUSIONS OF THE TEST CAMPAIGN .......................................................................................... 19

7 DEFINITION, SYMBOLS AND ABBREVIATIONS ................................................................................ 20

8 DOCUMENT HISTORY .............................................................................................................................. 22

9 REFERENCES ............................................................................................................................................... 23

10 APPENDIX A: FS LINK EXAMPLE PARAMETERS ........................................................................... 24



1 EX E C U T I V E SU M M A R Y This deliverable completes the outcome of Task 4.4 “Formal Test and Demonstration,” in which the formal test demonstration is executed on a subset of the full test set identified in Task 4.3. In particular, this document reports the recorded results of the test cases as defined in D4.2, [1], while D4.4, [2], provided the full lab setup integration and the details of the implemented equipment is presented and explained.

The results shown in this deliverable are related to the defined performance indicators.

This document summarizes the step-by-step test cases that are performed running through the test cases as defined in D4.2. The platform used is the dedicated CoRaSat lab test platform, as documented in D4.4.

This document concludes WP 4, related to the demonstration of the CoRaSat system.



2 SC O P E A N D ST R U C T U R E O F T H E DO C U M E N T The formal test and demonstration document provides a record and the related results of the outcome of WP4 activities on the demonstration of the CoRaSat system. This includes mainly all the results of the eight defined test cases and the resulting experimentation records, as well as the results derived in terms of expected system level gains and performance results as based on the key performance indicators defined in the project (see D4.1, [3]).

The test procedures, defined in D4.2, are followed and the test setup is explained and documented in D4.3 and D4.4, [4], [2]. The lab test setup consists of an adapted real two-way satellite test platform and end-to-end application demonstrations.

This document is organized as follows.

In Chapter 3, the test procedure defined in D4.1 and D4.2 are briefly summarized.

Chapter 4 provides the test results records for each of the considered use cases.

In Chapter 5, the resulting performance indicators are reviewed and discussed.

Finally, Chapter 6 concludes this document

Appendix A provides some FS link parameters used for the demonstration of Scenario C.



3 TE S T PR O C E D U R E RE V I E W The test procedures used for the demonstration follow the storyboard cases defined in D4.1 and use the test procedure steps defined in D4.2. The platform is configured in such a manner that the verification of the key performance indicators is performed as required.

The defined test cases from document D4.1 are outlined in the following. These are followed in the execution of the D4.5 tests and used to define the resulting results documented in the sequel.

Table 1 - Test procedure used for demonstration.

Test procedure used Test procedure #1 – Installation and deployment of a network of terminals within a cognitive zone close to a FS link or BSS uplink with database support. Test procedure #1 – Change the FSS network configuration of the FSS terminal in incumbent user link interference presence (in cognitive zone). Test procedure #2 – Measure network efficiency with and without RA technique usage. Test procedure #3 – Detect interference present from the incumbent user on the forward link. Test procedure #4 – Detect interference present from the incumbent user on the forward link. Test procedure #5 – Change the forward link carrier allocation according to incumbent user interference presence. Test procedure #6 – Measure interference levels from configured FSS system on the return link at the FS receiver. Test procedure #7 – Change the return link carrier frequency, power and rates according to incumbent user environment. Test procedure #8 – ESOMP movement through the coverage area.

.



4 TE S T CA S E S RE S U L T S RE C O R D S In the following, we go systematically over the storyboard scenarios as defined in D4.1 and follow the test procedure details of the test plan document, D4.2.

The user interface implemented in the course of the work in Task 4.4 has been used to perform these test tasks.

4.1 Test Results – Use case #1 Place the terminals in the locations to be emulated.

Specific locations of interest are considered, which cause particular interference conditions from FS links and are of interest for the Use case #1 demonstration.

These locations for the FSS terminals are outlined in the following table.

Table 2 - Forward link FSS terminal locations for the emulation.

Terminal Latitude [deg] Longitude [deg] ST-01 51.68 -0.09 ST-02 51.38 0.18 ST-03 51.52 -0.11 ST-04 51.71 -0.10 ST-05 51.38 0.19 ST-06 51.61 0.23 ST-07 51.52 -0.07 ST-08 51.31 -0.12

As a next step, the emulated carrier frequency is selected to emulate the interference environment desired. This configuration is considering the forward and return link carriers as defined in Table 3.

Table 3 - Carrier and bandwidth configuration in the forward and return links.

Carrier Carrier frequency [GHz] Bandwidth used [Mbaud] SatNet-1 / FWD-1 19450.0 30Mbaud SatNet-2 / FWD-2 17857.5 30Mbaud

The SatNet-1 frequency environment in the emulated geographic context is illustrated in Figure 1.

Before the configuration of the FS link interference is performed, the terminals are emulating only the end-to-end link budget conditions assumed in forward and return link.

The link conditions are then as follows for the recorded 8 terminals on the network:

• RTN: Return Path (from terminal to hub using HRC/MxDMA).

• FWD: From hub to terminals using DVB-S2.

The forward and return link parameters measured during the forward link budget emulation are provided in Table 4.



Figure 1 - Emulated interference context for SatNet-1.

Table 4 - Forward and return link parameters as measured when emulating the forward link budget.

Terminal Connection

Status

FWD C/(N+I)

[dB]

FWD Receive Level [dBm]

RTN C/(N+I)

[dB]

FWD Efficiency [bps/Hz]

RTN Efficiency [bps/Hz]

RTN Bitrate [bps]

ST-01 loggedOn 16.52 -42.3 10.89 3.70329 2.13 4226240 ST-02 loggedOn 16.53 -41.5 9.51 3.70329 1.94 4241280 ST-03 loggedOn 16.51 -41.8 10.36 3.70329 2.13 4226240 ST-04 loggedOn 16.61 -42.3 9.97 3.70329 2.03 4244288 ST-05 loggedOn 16.52 -41.7 9.55 3.70329 1.85 4223232 ST-06 loggedOn 16.53 -43.0 10.51 3.70329 2.22 4259328 ST-07 loggedOn 16.52 -43.0 9.86 3.70329 2.03 4244288 ST-08 loggedOn 16.49 -42.0 9.96 3.16562 2.03 4244288

From this initial status of the network emulated for a typical performance of a two-way satellite service, it can be noted that the following average efficiencies can be reached by the system.

Table 5 - Average efficiency reached by the system.

Forward link efficiency [bps/Hz] Return link efficiency [bps/Hz] Average efficiency 3.636 2.045

FS forward link interference:

From the database access and using the combined interference levels on the forward link from all in-band FS links for SatNet-1 and SatNet-2, the following levels for the interference into the FSS terminal reception are obtained.

At the same time the signal power levels emulated are as reported in Table 7.



Table 6 - Emulated interference levels from FS links into FSS reception.

Terminal Interference level at reception [dBm/

Bandwidth used] SatNet-1 / FWD-1

Interference level at reception [dBm/ Bandwidth used] SatNet-2 / FWD-2

ST-01 -131.69 < -200.0 ST-02 -130.06 < -200.0 ST-03 -125.19 -156.46 ST-04 -124.39 < -200.0 ST-05 -121.0 < -200.0 ST-06 -115.32 < -200.0 ST-07 -110.07 < -200.0 ST-08 -105.13 < -200.0

Table 7 - Reception signal power at FSS terminal input.

SatNet-1 / FWD-1 reception SatNet-2 / FWD-2 reception Signal power at reception -111.47 dBW/BW -111.48 dBW/BW

It should be noted that under no congestion conditions, the distribution of the terminals between the two forward links and the usage of the highest signal quality link is trivial. Switching on the FS interference leads to this context.

The resulting emulated signal to interference levels are outlined in the following.

Table 8 - Emulated interference levels at FSS reception for SatNet-1.

Terminal C/I level from FS interference

[dB]

Interference level at SatNet-1 reception input at FSS terminal

[dBm]

ST-01 21.00 -131.69

ST-02 19.38 -130.06

ST-03 14.51 -125.19

ST-04 13.70 -124.39

ST-05 10.32 -121.00

ST-06 4.64 -115.32

ST-07 -0.61 -110.07

ST-08 -5.55 -105.13

The application of the FS interference in the channel emulator leads to the terminal situation reported in Table 9.

The recorded spectrum sensing (SS-SNIR) interference levels as a result of the emulated FS link parameters are reported in Table 10.



Table 9 - Return link parameters as measured when emulating the forward link budget.

Terminal

Connection Status

FWD C/(N+I)

[dB]

FWD Receive Level [dBm]

FWD expected C/N.exp

[dB]

RTN C/(N+I)

[dB]

FWD Eff.

[bps/Hz]

RTN Eff.

[bps/Hz]

RTN Bitrate [bps]

ST-01 loggedOn 14.70 -42.3 16.52 10.22 3.70329 1.94 4241280 ST-02 loggedOn 12.80 -41.5 16.53 10.65 3.16562 2.03 4244288 ST-03 loggedOn 10.60 -41.7 16.52 9.79 2.47856 2.03 4244288 ST-04 loggedOn 9.00 -42.1 16.52 9.65 1.98064 2.03 4310464 ST-05 loggedOn 7.70 -41.4 16.53 9.23 1.78861 1.94 4304448 ST-06 loggedOff 0.00 X 16.52 0.00 X X X ST-07 loggedOff 0.00 X 16.52 0.00 X X X ST-08 loggedOff 0.00 X 16.53 0.00 X X X

Table 10 - Signal to interference levels as emulated and recorded by the spectrum sensing (SS-SNIR) mechanism for the emulated context.

Terminal Emulated interference level as derived from database access

C/I .DB [dB]

Measured interference level from FS link as derived from SS-SNIR spectrum

sensing algorithm C/I .SS [dB]

ST-01 21.00 19.36 ST-02 19.38 15.20 ST-03 14.51 11.38 ST-04 13.70 9.85 ST-05 10.32 8.31 ST-06 4.64 0.10 ST-07 -0.61 0.10 ST-08 -5.55 0.01

Efficiency records for the forward and return link are as follows:

Table 11 - Forward and return link efficiency after the application of the FS interference levels on the channel (excludes ST-06, ST-07 and ST-08, which are logged out).

Efficiency in terms of [bps/Hz] Forward link efficiency 3.0284 Return link efficiency 1.20

The terminals ST-06, ST-07 and ST-08 are after this FS interference emulation reallocated to SatNet-2. This is a result of the fact that the FS interference is so high in this particular example at the reception of these terminals that the link is lost. The FSS hub detects this link loss on the normal controller. The FSS controller systems can then react and redirect these terminals to use another forward link. It is verified and noted as test result that this occurs without intervention on the terminal side and this re-provisioning is fully automated on the hub side.

Efficiency records for the forward and return link are as follows:



Table 12 - Forward and return link efficiency after the application of the FS interference levels on the channel (excludes ST-06, ST-07 and ST-08, which are logged out).


4.2 Test Results – Use case #2 (Spectrum sensing) In order to test the spectrum sensing (SS-SNIR) method, the used setup configured is started with the initial conditions as defined in the use case #1 context.

From this, the interference level into one terminal is changed and this while the SS-SNIR algorithm is running on the gateway emulator side.

Figure 2 - Emulated illustration of the context for the terminal ST-01 before and after applying the emulated interference for ST-01.

Figure 3 - Measured forward link levels for the application of the spectrum sensing (SS-SNIR) method with emulated fading on terminal ST-01.

It is noted from these test results that the spectrum sensing detection is indeed providing the measurement of a degraded link because of interference, which is indicated to the operator (red flagged terminal ST-01) and on the measured level of the C/I.SS of 8.20dB.

The ST-01 terminal is then reset to its original state. As cross verification the fading event is emulated (configured fading time series is applied and a manual test with a changed signal level).

As a result the link is also degraded but the C/I.SS is maintained at the expected initial level.



4.3 Test Results – Use case #2 and #5 (DB reconfiguration) This test covers the use case #2, change network configuration of FSS terminal in incumbent user link interference presence as well as the use case #5, changing the forward link carrier allocation according to incumbent user interference presence.

The change in terminal position is tested on the configuration of the system.

An alternative terminal location is configured for the following terminals.

The change is performed and the database access and interference computation resulting from the change is performed in the expected manner.

The change of terminal position, emulating a change in provisioning, triggered as expected a change/update in the interference level expected per terminal. The changed terminal position for this test is outlined in the following table:

These locations for the FSS terminals are outlined in the following table.

Table 13 - Forward link FSS terminal locations for the emulation.

Terminal Latitude [deg] Longitude [deg] ST-01 51.50 -0.33 ST-02 51.31 -0.12 ST-03 51.73 -0.47 ST-04 51.46 0.01 ST-05 51.39 -0.39 ST-06 51.62 0.15 ST-07 51.57 -0.48 ST-08 51.74 -0.16

With this test it is formally verified that the emulated context is correctly updated when the terminal position is changed or when the forward link frequency is changed in the system. The change in the forward link frequency in this case is from the initial configured 19450.0MHz to 18865.5MHz with also 30MBaud forward link rate assumed.

Table 14 - Forward link interference levels computed after changing the terminal locations and the SatNet-1 frequency settings.

Terminal

Initial interference condition for SatNet-

1 [dBm/BW]

Interference level [dBm/BW] at changed location for SatNet-1

Interference level after changing the SatNet-1 /

FWD-1 [dBm/BW]

ST-01 -131.69 -146.27 -153.45 ST-02 -130.06 -105.13 < -200.0 ST-03 -125.19 -166.83 -148.53 ST-04 -124.39 < -200.0 < -200.0 ST-05 -121.00 < -200.0 < -200.0 ST-06 -115.32 -157.97 < -200.0 ST-07 -110.07 < -200.0 -164.16 ST-08 -105.13 < -200.0 < -200.0



A new database access is then performed and the interference levels at the reception of the FSS terminals are measured and updated as expected. This is reported in Table 14 for the emulated scenario considered in the formal test case run.

From these tests, we can conclude that the automated database access is working as a response to the provisioning of new terminals, which is emulated in this case by changing the terminal location and then trigger a new database (DA) access for the computation of new interference limits. We also demonstrate the possibility to access the database information from different forward link configured frequencies among the emulated list of 20 possible SatNet / FWD link frequencies by selecting a different emulation context for the forward link frequency. Also in this case a database access is performed and results in the expected aggregate interference computation per terminal on the FSS gateway emulator side.

4.4 Test Results – Use case #3 – Measure network efficiency without and with Resource Allocation (RA)

Applying the resource allocation to the defined emulated context illustrates the forward link capability to optimize the link under the constraints of the interference and resource limitation of the system.

We give one practical example in the context of these tests here.

Starting from the initial condition as the outcome of the test case #1, the network is configured as follows.

Figure 4 - Initial condition for the emulation of the test case #3 (outcome of the test case #1).



Figure 5 - Test condition at the outcome of use case #3 test execution with 7 terminals on SatNet-2 and 1 terminal on SatNet-1.

Perfoming the resource allocation (RA) method on the forward link leads to the following recommendation by the system: Redirect to SatNet-2 the terminals ST-01, ST-02, ST-04 and ST-05.

This RA action is executed by the network control center.

After the execution of the redirect command, the following confdiguration is reached and the efficiency measured.

The resulting efficiency on the entire network average is reported in Table 15.

Table 15 - Efficiency at the outcome of the test case #3 execution, after applying the resource allocation (RA) on the forward link.


From these results it can be concluded that the resource allocation (RA) on the forward link results in an increase in efficiency of around 16% compared to the overall network efficiency without resource allocation used.

4.5 Test Results – Use case #4 and # 6 This use case covers the detection of interference present from the incumbent user on the forward link and the measurement of interference levels from configured FSS system on the return link at the FS receiver.

The detection of the interference at the input of the incumbent user is performed by emulating the path from the FSS terminal locations to the FS receiver input.

For that purpose the FSS terminal locations are changed to approach the FS receiver in order to create an interference context of interest for this scenario #4.



Figure 6 - Emulation of the context for the FS link reception interference assessment.

It should be noted that, in this configuration, all terminals are within the close proximity of the FS link receiver in order to emulate interference levels that are measurable for the context emulated here.

The terminal locations and FS receiver locations emulated are considered in close proximity for this test.

It is noted that the standard terminal antenna and FS receiver antenna assumptions apply for this test and evaluation of the FS link. The evaluation of the return link emulation settings is outlined in Appendix A. The attenuator settings of the return link emulator are set in such a manner that the link towards the FS receiver corresponds to the expected relative attenuation level.

For the emulation of the return link, a relative approach is considered here. The spectrum analyzer reference level is an assumed level that would in practice correspond to the applicable limit, such as the applicable ITU-R level of -150dBW/MHz at the FS receiver input.

Such a limit is assumed at the FS receiver input. Here the blue line of the following spectrum analyzer measurement plot corresponds to this assumed limitation at the FS receiver input.

The emulated interference level is measured accordingly in this example to be -160dBW/MHz to -155dBW/MHz for the transmitting terminals power density, relative to the assumed limit level.

Figure 7 - Interference level emulated at the FS link receiver.



In this configuration it is shown that the assumed interference context respects the FS receiver interference limitation with a measured margin of about 5dB.

4.6 Test Results – Use case #7 – Change the return link carrier frequency, power and rates according to incumbent user environment

For this test we start from the configuration as defined in the use case #4 contexts with the return link measurements applied to the transmission and with the applicable limit also shown.

The interference from the FSS terminals onto the FS receiver were not reaching the maximal limitation allowed and about 5dB additional margin was possible in this return link configuration.

Assuming the limit of the FS receivers is well known to the FSS system, the application of the resource allocation on the return link can be applied.

In this context we test the implemented return link resource allocation (RA).

The starting condition here is the power limit and the bandwidth used by the return link carrier group for this test.

Both starting and final conditions for the return link RA method are outlined in the following table.

Table 16 - Return link resource allocation at start and after the RA algorithm convergence for the applicable FS link limit considered.

Parameter measured Before RA on return link After RA on return link RCG power allocation limit applied

-120dBW/MHz -105dBW/MHz

RCG bandwidth allocation required to reach SLA of 4Mbps / terminal

26.1MHz 7.65MHz

Return link efficiency 2.03 bps/Hz 4.16 bps/Hz ModCod used on return link 11 - 14 45 C/(N+I) measured on return link 4.8dB - 6.4dB 17.0 – 19.0dB Transmit power levels range configured on return link terminals

-32dBm to -29dBm -24dBm to -22dBm

It should be noted that here we assume that the terminals are capable of the additional dynamic range in terms of higher transmit power allocated required for the higher power configuration. In practice (in the field) there could be additional constraints in terms of EIRP limitations as well.

For this test result, the measured link limitation on the spectrum analyzer can be verified. Since the setup is calibrated and the assumption of a well-known limit at the FSS gateway was applicable, it can be verified as well that this is indeed reached as expected on the spectrum analyzer (FS reception emulator plot) as shown on the following figure.

This test concludes the return link RA as a possible method to implement a known FS link limitation in this satellite network in which all return link transmissions are centrally controlled and managed through the return link controller and using the flexibility and efficiency of the HRC/MxDMA technology from Newtec.



Figure 8 - Measured FS link interference levels after resource allocation (RA) on the return link.

4.7 Test Results – Use case #8 – ESOMP movement emulation through coverage area

The ESOMP movement is emulated using a step-by-step emulation of the terminal locations through the coverage area and the successive measurement records at different intermediate locations through the positions of the emulated trajectory on the link.

For the ESOMP testing a specific terminal has been connected to another special channel emulator, which is capable of simulating the Doppler impact on the forward link as well as on the return link for the assumed speed and uplink and downlink frequencies assumed.

This setup has been thoroughly tested on the CoRaSat platform with a dedicated ST-M1 (mobile 1) terminal in an emulated loop for the terminal movement for typical speeds for vehicular, aeronautical, train and maritime SatCom on the move applications.

With the support of this setup the Doppler frequency offset compensation was implemented on the platform and the demodulator behavior for the return link was adjusted to work under ESOMP typical link conditions.

The applied cognitive techniques are working in a similar manner as for fix FSS terminals. The reaction time in the emulated CoRaSat platform for the cognitive techniques allows in its current implementation only static snapshots of the reaction of the terminal for the communication on the move.

It should be noted that in practice sufficient margins can be applied so that both the forward link to the FSS terminal (scenarios A and B) as well as on the transmit side (scenario C) so that no interference is caused and no service interruption experienced.

A key outcome of the ESOMP experiments as well is that the terminal location has to be sent regularly to the network control center (NCC) for the correct application of the frequency assignments given the interference environment. In case the ESOMP terminal logs on from an unknown initial location, an alternative is that the terminal logon procedure is changed for the ESOMP case to first logon on a dedicated capacity in the exclusive frequency bands. During the operation, when the location and trajectory (predicted location) of the terminal is known to the network control center, it can be redirected to other frequency bands using sufficient margins to switch to non-interfering carriers during operation.



5 RE S U L T I N G PE R F O R M A N C E IN D I C A T O R S On the performance indicators devised for the evaluation of the tests, it can be concluded that the application of the cognitive techniques as applied in this example scenario considered resulted in the following outcomes:

• The forward link performance in terms of service level agreement (SLA) is fully reached under the considered interference conditions. The configured CIR rates of 10Mbps per forward link could be reached as expected.

• The overall link average efficiency could be improved using the cognitive techniques devised in the context of CoRaSat, such as the database access (DB) to enable the FSS system’s awareness of the FS link interference and resource allocation (RA) in order to improve the efficiency on the forward link. The reached efficiency gains using these techniques are measured to be around 16.5%, from 3bps/Hz to around 3.5bps/Hz.

• For the return link the interference onto the FS incumbent link’s reception has been emulated and measured. The resulting applicable FS link limit has been assumed to be known to the FSS system central controller unit to allow the management of the resources according to the applicable transmit power limitations.

• From the measured results, it can be concluded that in this case also the limit can be reached and maintained as expected at the FS link reception input, provided the setup is well known to the cognitive FSS system transmit management system. In case this is not fully known or a practical uncertainty has to be considered, this can be managed in terms of additional margins that can be implemented in a straightforward manner in the system to allow for a safe operation.

• The end-to-end data is activated to measure the impact of the links emulated on the forward and return link on the user experience. A 10Mbps forward link and a 4Mbps return link was activated for the test purposes.

It is noted that the HRC/MxDMA method performs the return link reconfigurations required in the context for the CoRaSat return link resource allocations (RA) while keeping the link established and with minimal losses on the traffic.

The forward link reconfiguration in this case was emulated with a fully automated terminal provisioning for the switching between the two configured SatNet contexts. This is performed with a “simple switching” function but with a link interruption in this implementation, as the terminals need to reacquire the links after the switching. A further improved version of this process is currently under development.



6 CO N C L U S I O N S O F T H E T E S T C A M P A I G N The work performed within the work package 4 of the CoRaSat project results in a practical lab demonstration of the end-to-end FSS network in presence of potential incumbent users in the emulated scenarios B and C. It should be noted that from the previous work within CoRaSat the scenario A can be considered in a similar context as scenario B in terms of impact on the FSS system. With this all CoRaSat specific scenarios contexts (forward and return link) were tested and verified in the context of this test campaign.

This formal test campaign verifies the implemented CoRaSat emulator functionality and capabilities. It also demonstrates the implemented cognitive techniques as test functions in a dedicated CoRaSat controller for the test emulator setup. This includes the emulation of a database access (DB) to compute the expected interference level for the FSS terminal forward links in a geographic context, which is realistic and based on a real database data available for these links.

Furthermore the cognitive technique on the forward link of resource allocation (RA) is evaluated. The tests concluded here a clear efficiency improvement in the order of magnitude as expected when applying the RA method. It is to be noted that in practice there can be additional limitations and service requirements, such as contention ratio limits on the forward links and more complex SLA definitions including not only a CIR (constant information rate) but also a peak rate (PIR) committed per terminal. There additional service level limitations can be included in the resource allocation method to fully take into account the network optimization in a practical system. This would be the case in a commercial implementation of the method.

The spectrum sensing has been tested in view of potential unexpected interference impacts from incumbent users, which has not been reported by the database for example or which has unexpected levels for some reason (e.g. fault or reconfiguration of the incumbent system). The spectrum sensing (SS-SNIR) technique devised in this case relies on the centralized collection and analysis of measurement data from all terminals and it was demonstrated that this method is well capable of detecting the interference and also of distinguishing the interference from other events that could occur on the network such as fading or gain changes (e.g. antenna de-pointing for example).

On the return link the possibility to maintain a certain FS receiver limitation in terms of power density at the reception is demonstrated in the context of these tests. This is performed with the assumption of the FS receiver location and parameter knowledge, however without any external measurement feedback. The demonstrated capability of the return link reconfiguration is based on the calibration and correct configuration of the system. The highly flexible and efficient return link used was shows to be well capable of reconfiguring the link in a centralized and coordinated manner for all the terminals in the network.

The work within work package 4 of the CoRaSat project therefore demonstrates as expected the technical feasibility of the proposed concept as well as the feasibility of the proposed cognitive techniques. For the scenarios A and B there the practicality of using an FSS system in these bands is considered well feasible. For scenario C the assumption of the perfect knowledge of the FS link receiver deployment can indeed be problematic in practice and therefore it is to be revised carefully.



7 DE F I N I T I O N, SY M B O L S A N D AB B R E V I A T I O N S

ACM Adaptive Coding and Modulation

AUPC Automated Uplink Power Control

ACI Adjacent Channel Interference

CE Channel Emulator

CQI Channel Quality Information

CR Cognitive Radio

CS Compressive Sensing

CSI Channel State Information

CENELEC Centre for Electro Technical Standards

DB Database

DCA Dynamic Capacity Allocation

DVB Digital Video Broadcasting

DVB-RCS DVB with Return Channel via Satellite

DVB-S DVB via Satellite

DVB-S2X DVB via Satellite version 2 extension

EBU European Broadcasting Union

ETSI European Telecommunications Standards Institute

E-UTRAN Evolved UMTS Terrestrial Radio Access Network (a.k.a LTE)

FC Fusion Center

GWe Gateway Emulator

HRC High Resolution Coding

IA Interference Alignment

IC Interference Cartography

IDW Inverse Distance Weighted

LRT Likelihood-Ratio Test

LTE Long Term Evolution

LTE-A LTE Advanced

MAC Medium Access Control

MIMO Multiple Input Multiple Output

MODCOD Modulation and (channel) Coding

MxDMA Multi-dimensional dynamic medium access

NCC Network Control Centre

RA Resource Allocation

REM Radio Environment Map

RCST RCS subscriber

RF Radio Frequency

RLC Radio Link Control

RSS Received Signal Strength



ST Satellite Terminal

SS-SNIR Spectrum Sensing SNIR

SNIR Signal to noise and interference ratio

SIN Satellite Interactive Network



8 DO C U M E N T HI S T O R Y

Rel. version Date Change Status Author 1 0 30/09/2015 First release to the European Commission NTC



9 RE F E R E N C E S

[1] CoRaSat (COgnitive RAdios for SATellite Communications), FP7 ICT STREP Grant Agreement n. 316779, D4.2 “Test Plan Document,” 2015.

[2] CoRaSat (COgnitive RAdios for SATellite Communications), FP7 ICT STREP Grant Agreement n. 316779, D4.4 “Integration and Testing,” 2015.

[3] CoRaSat (COgnitive RAdios for SATellite Communications), FP7 ICT STREP Grant Agreement n. 316779, D4.1 “Proof of Concept Storyboard,” 2014.

[4] CoRaSat (COgnitive RAdios for SATellite Communications), FP7 ICT STREP Grant Agreement n. 316779, D4.3 “Test Set Implementation,” 2015.

[5] Newtec Cy, DIALOG© Product Description, http://www.newtec.eu/product/newtec-dialog [accessed 20 May 2015]



10 AP P E N D I X A: FS L I N K EX A M P L E PA R A M E T E R S For the scenario C emulation (use cases #4, #6, #7), the return link interference emitted towards the FS link receiver is measured.

The parameters used are outlined in the table here below. CORASAT-WP4-ScenarioC-FSreceiveinputinterferencelevelassessment

ComputationalongITU-RRECP.452-15References

Frequency(RF) 27.7 GHz ITU-RRECP.452-15DistanceFSS-FS 8.9 km ITU-RSF.1006Gaseousattenuation 0.0 dB

LineofsightpropagationFSStoFS140.3 dB

FSSLatitude 51.5000 degNorth SatAltitude 35793000 mFSSLongitude -0.1900 degEast EarthRadius 6378000 mSat.Position 13.0 degEast EStoSatdist 38639813 mAlpha 0.92FSS_Elevation 29.8 degFSS_Azimuth 163.3 degFSS_ES_height 0.0 m

FSreceiverheight 10.0 mFSlongitude -0.1900 degEastFSlatitude 51.5800 degNorthFSAzimuth 0.0 degFSElevation 0.0 degFSStransmitpower 50.0 dBWBaudrateFSS 2.0 MbaudOccupiedbandwidth(FSS) 2.12 MHzTransmitPowerdensity(FSS) -13.3 dBW/Hz FSSEarthstationon-axisEIRPspectraldensityindBW/Hz

AzimuthlookangledifferenceFS-FSSantennas(dAZ)DeltaAzimuth -163.3 degrees

ElevationlookangledifferenceFS-FSSantennas(dEL)DeltaElevation -29.8 degrees

AntennagainofFSreivertowardsFSStransmitterCombinedangle -30.9 degrees

-30.90 degrees1239

FSSantennagaintowardsFS 13.7 dBiFSantennagaintowardsFSS 0.0 dBi

InterferencelevelatFSreceiveinputfromoneFSStransmitterminal-185.5 dBW/Hz-155.5 dBW/MHz

ApplicableLimits(accordingtoITU-RSF.1006)Themaximumpermissibleinterferencepowernottoexceed20%oftimeattheFSSreceiver,calculatedaccordingtoITU-RSF1006,is-150.8dBW/MHz.Thecalculatedshortterminterferencenottoexceedfor0.003%oftimeis-138.1dBW/MHz.

SettingfortheattenuatorforthepathbetweenFStransmitandFSSreceiver

Referencelevelassumedisconfigurable:-145 dBW/MHz

Relativeattenuatorsettingbasedonassumedreferencelevelconsidered-10.5 dB

Table 17: FS receive level evaluation with the related computation of the attenuator settings for the link emulation.

deliverable d4.5 formal test demonstration · release 0.01 (final draft) pag. 7 of 24 4 test cases...

Documents