1. 1 OFDMA Module Usage within Seamcat

2. Summary 2  Using generic or OFDMA model when addressing compatibility/sharing studies?  Pointing out differences between both models  Being able to build common configuration for both scenarios

3. Using Generic/OFDMA model when addressing compatibility/sharing studies 3 Subject: Impact of Mobile Service on another/the same service within Seamcat Specific OFDMA ModuleGeneric Module Which module should be used and Why?

4. Using Generic/OFDMA model when addressing compatibility/sharing studies 4 An example: Specific OFDMA Module was used for Interfering Links Simulation of potential interference from LTE UL to DVB-T & determination of UE OOBE level

5. Using Generic/OFDMA model when addressing compatibility/sharing studies 5 An example: What happens if we replace OFDMA Module by Generic? Simulation of potential interference from LTE UL to DVB-T & determination of UE OOBE level

6. Using generic/OFDMA model when addressing compatibility/sharing studies? 6

7. Highlighting differences between two modules 7 Where? Interfering Links Specific OFDMA ModuleGeneric Module

8. Highlighting differences between two modules 8 OFDMA Module case Task 2: How can we calculate the Number of mobile (User Equipment UE) per base station (BS)? Task 3: If UE uses 1 Resource Block (RB) or all RBs, should we use the same emission mask for it? Task 4: Since only one emission mask (9 MHz) can be used, how many UEs/BS should we simulate? Task 5: According to Task 4, update value of one parameter in OFDMA General Settings. General settings

9. Highlighting differences between two modules 9 OFDMA Module case Task 6: Regarding the Number of BSs in the system and the Cell layout in the System Panel, how many BSs per cell do we have? Task 7: From Tasks 5 & 6, how many UEs per cell do we have in this scenario? Task 8: Which device from the Interfering Links can be positionned related to one victim device (Tx or Rx)? Positioning Transmitter to Victim Link Receiver Path

10. Highlighting differences between two modules 10 Generic Module case Task 9: Which device from the interfering links (Rx or Tx) can be positionned related to one victim device (Tx or Rx)? Task 10: Is that possible to tune the Number of active transmitters (UEs in this case)? Which Modes do make this parameter active? Task 11: We need also to simulate distance(UE, Rx victim ). Which Mode is the only one enabling such tuning? Task 12: Which Position relative to should we define? Transmitter to Victim Link Receiver Path

11. Is that possible to reach common configuration for different scenarii? 11 Task 13: According to Tasks 8 and 9, which configurations could lead to common position for both scenarii? Task 14: Explain through the Minimum Coupling Loss (MCL) concept why BS and UE cannot be set up at the same place. Conclude that if Rx victim and BS can be located at the same position, common setting is possible for both scenarii. Task 15: Update position of Interferer UE for different modules in order to get the common configuration Position Interferer/VictimBS/RxVUE/RxV ModuleOFDMA Generic

12. Is that possible to reach common configuration for different scenarii? 12 Run the scenario with OFDMA Module Look at the Simulation Outline. Task 16: Do we see LTE UE position on the graphic?

13. Is that possible to reach common configuration for different scenarii? 13 Since LTE UE position /Rx victim is unknown, we need to find another way for deriving the distribution of the Path distance factor in the scenario with Generic Module. Task 17: Save previous parameter settings (from previous Tasks) Run the simulation and compare Unwanted/Blocking iRSSs from OFDMA module to Generic one. → As results are still different, the distribution of the path distance factor for the Scenario with Generic Module needs to be updated!

14. Is that possible to reach common configuration for different scenarii? 14 In order to assess the distribution of the LTE UE position over random events (in OFDMA Module) so that we integrate it in the Generic Module, we could base on Effective Path Loss (EPL) parameter of the Interfering/Victim link UE/Rx victim. Min EPL= Minimum Coupling Loss (MCL) 3GPP TR 36.942: An important parameter to be defined is the minimum coupling loss (MCL). MCL is the parameter describing the minimum loss in signal between BS and UE or UE and UE in the worst case and is defined as the minimum distance loss including antenna gains measured between antenna connectors. As MCL depends on GRx and GTx, if one of those gains is not constant, antenna discrimination needs to be assessed at any event /derivable when generating random data given that azimut random distribution, however we cannot access azimut for each event.

15. Is that possible to reach common configuration for different scenarii? 15 GTx is the gain of UE, assumed to be isotropic. However, GRx victim is not isotropic. Task 18: Set GRxvictim to isotropic by unticking horizontal/vertical pattern. → Assumption: isotropic antenna gain for Rxvictim. From the Seamcat results, it is possible to derive I arg so that P(Interference≤Iarg)=95%. When GRx, GTx are constant, we manage to calculate darg=φ(Iarg) from the PathLoss.

16. Is that possible to reach common configuration for different scenarii? 16

17. Conclusions & Prospect 17 Both scenarii may lead to common results with suitable parameters setting. Each Module has its own specificity, specific scenario may be run from only one Module Looking at glance on Simulation Outline helps to check the relevance of the selected scenario. Future Improvements of Seamcat will help any user to ‘check’ some parameters for debugging (e.g. being able to extract distance between 2 devices for each random event from the Interference iRSS) Future Improvements of Seamcat could work on enabling use of different Emission Masks (when available in the Library) depending on the RBs amount allocated to each UE.