1. Extensions, System Outline and Correlation Modes and
System Plugins (SP)
Extensions, System Outline and Correlation Modes and

2. Victim Specific Interference Link Settings System Outline
Presentation outline
SP Extensions:
Interference Names
Victim Specific Interference Link Settings
System Outline
Correlation Modes

3. SP extensions
InterferenceNames.java : in addition to the default ones (iRSS Unwanted (summation) and iRSS Blocking (summation), it is possible to add new names using this interface:
title: corresponds to the title of the panel, e.g. ‘Average over the UEs in reference cell’
information: is the tooltip next to the title
unwantedName : is the name for the line corresponding to iRSS Unwanted
blockingName : is the name for the line corresponding to iRSS Blocking

4. SP Victim Specific Interference Link Settings
Each interference link can have its own configuration, which is related to the interfering SP and interference link.
Sometimes there is need for a victim specific configuration per interference link. In that case, the following interface must be extended on the SystemPlugin.java:
The SP will return a list of AsVictimInterferingLinkDefinition that represent a specific configuration per interference link.

5. SP Victim Specific Interference Link Settings AsVictimInterferingLinkDefinition
The interface AsVictimInterferingLinkDefinition.java implements the following methods:
getName: The name as it will appear in SEAMCAT
getInformation: A detailed description of what the panel does. It will show as a popup window.
getUIClass: The UI definition as a standard plugin input interface.
This feature is currently used only for OFDMA UL to configure specific path loss settings.

6. SP System Outline
The interface SystemOutline.java gives the plugin developer the capability of drawing a defined collection of shapes that can be used in the scenario and that are displayed in the panel called ‘Event Results’:
The system outline is used for the display of a simulated event when a simulation is completed only for the last event. It is recalculated if a particular event is replayed.

7. SP Correlation Modes
Correlation modes are algorithms to position the interfering systems relative to the victim system.
The victim system is always placed independently and the interfering systems can have a relative position with respect to the victim system.
'Mode': selection of the positioning algorithm.
'Reference component' and 'Position relative to': define the starting and end point of the correlation vector.
'Delta X, Y’: defines an offset distance that is added to the value specified in a correlation mode.
'Minimum coupling loss': defines distances below which is not logical to place any VLT.

8. SP Correlation Modes
Correlation settings involve both the victim and interfering system
The settings presented to the user in the above UI panel depend on the implementation of the victim and interfering SPs.
Correlation modes are an optional extension to an SP. If not implemented, SEAMCAT will use the built-in correlation modes (None and Correlated).
For their implementation, a SP needs to extend the interface CorrelationDefinitions.java.

9. SP Correlation Modes
The methods getCorrelationModes, getInterfererTargetPointNames, and getVictimCorrelationPoints map directly to the first three inputs of the UI:
SEAMCAT will call the interfering SP on its getCorrelationModes and will extend additional correlation options in the dropdown box called 'Mode'.
SEAMCAT will call the interfering SP on its getInterfererTargetPointNames and populate the dropdown box 'Reference component' with the values returned.
SEAMCAT will call the victim SP on its getVictimCorrelationPoints to populate the dropdown box 'Position relative to'.

10. SP Correlation Modes : Implementation in the Generic System
These are the definition of the above methods as implemented in the Generic System:

11. SP Correlation Modes : Implementation in the Generic System
When an SP is configured as victim the method getVictimCorreltaionPoints is used to propagate the selectable values in the 'To position with' dropdown box.
The selected value is then translated into an actual position during the simulation. This is handled by the method getVictimPosition.
Below is shown how the Generic System maps the victim correlation points to actual coordinates:
It takes the first LinkResult of the collected victims (the Generic System will always only collect 1 victim) and if 'VLR' is chosen, it returns the position of the VLR antenna. Otherwise, it returns the position of the VLT antenna

12. SP Correlation Modes : Implementation in the Generic System
The ISE uses the information of the previous slides to the position of the interfering system:
getPositionRelativeTo(): gets which is the reference component (e.g. VLR)
getVictimPosition(vCollector, relativeTo): gets the position of the victim.
getCorrelationMode(): gets the correlation vector.
trialDelta(): gets any offset (x,y).
Finally it adds all these distances to obtain the position of the interfering system.

13. SP Correlation Modes : Defining a Correlation Mode
The ISE calculates the position of the interfering SP as follows:
The correlation mode generates the vector in the diagram resulting of the addition victimPos.add(deltaVector).add(correlationVector)
The interface to implement when defining your own correlation mode is CorrelationMode.java:

14. SP Correlation Modes : Custom Correlation UI
Custom Correlation Modes need a specific UI that can be added by the SP by extending another optional interface: the CustomCorrelationDefinitions.java
This interface allows the plugin developer to customize the UI for the different Correlation Modes.
The Generic System uses this, as can be seen in the below code:

15. SP Correlation Modes : Custom Correlation UI
These extra inputs can be seen in SEAMCAT when the interfering SP is a Generic System. For example, when the mode Uniform is selected we obtain:
The 'Relative Positioning' is always shown regardless of the mode.
The three next panels Mode 'Uniform density' Configuration, Active Transmitters and ILR at Center are shown because of selecting the mode Uniform.
The last panel, called Co-Location Configuration is activated when the interfering SP allows to be co-located. This is described in the following section.

16. SP Correlation Modes : Custom Correlation UI. Allow Collocation
In the CorrelationDefinitions.java it is also possible to specify if the SP supports co-location, i.e. when this SP is configured as an interfering system it is possible to override the correlation settings with the settings from another interference link
If this is supported, it returns true from the method allowCoLocation.

17. SP Correlation Modes : Custom Correlation UI. Allow Collocation
In this scenario there are two interference links (Link 1 and Link 2).
If Link 2 is selected (with Generic system as interfering system), it needs to support co-location and therefore the 'Co-Location Configuration' panel is displayed. This allows the selection of another Link 'To position with'.
By selecting Link 1 the only relevant inputs are the delta x, delta y, and minimum coupling loss – the rest of the correlation configuration will rely on that of the Link 1
When co-location is enabled, the ISE processes first all non co-located interference links and then all co-located links.
The code above shows the loop on the InterferingResultCollector of the SP by which the current link is co-located with. It loops through all collected Interferers and picks out the LinkResult which holds the tx and rx positions that the interfering SP must use when positioning its tx and rx. It is actually a mistake to pass the position because the LinkResult holds all position information needed.

18. Questions?