12.6 Simulation Group Feature Object
12.8.1 How to Access GSM Interference Matrix Feature Objects
The ObjectKind property for an Interference Matrix ChildFolder objects is: {5144E1F9-E539-4F8C-BC0C-49A11C6389E8}
Interference Matrix ChildFolder objects are children of the folder named "Interference Matrices".
GSM Interference Matrix Feature objects are available through the Dispatch property of Interference Matrix ChildFolder objects:
12.8.2 get_Source
Returns the "Interference Matrices" ChildFolder object.
Parameters
[out] ppSource: Address of the IDispatch interface pointer used to return the "Interference Matrices" ChildFolder object.
12.8.3 Load
Loads an interference matrix.
Remarks
This method must be called before any access to an interference matrix.
12.8.4 CompleteScopeInfo
Completes scope information.
Remarks
This method must be called after transmitters are added to the scope.
12.8.5 get_Scope
Returns the scope of the interference matrix.
Parameters
[out] ppTable : The address of the ITabularData interface pointer used to return the scope of the interference matrix. Dim oInterferenceMatrix
Dim oInterferenceMatricesChildFolder Set oInterferenceMatricesChildFolder
= oDocument.GetRootFolder(atoData).Item("Interference Matrices") Set oInterferenceMatrix = oInterferenceMatricesChildFolder.Dispatch
HRESULT get_Source(IDispatch **ppSource);
HRESULT Load();
HRESULT CompleteScopeInfo();
Remarks
The scope of an interference matrix is a Tabular Data object containing a mapping from the row identifier for a transmitter to the following information:
The coverage percentage as victim, and as interferer. The default values are 100.
The BSIC and BCCH when the interference matrix information was collected. The default values are -1.
12.8.6 put_Active
Sets the active state.
Parameters
[in] isActiveVal : The VARIANT_BOOL value used to specify the active state of the interference matrix.
Remarks
An active interference matrix is used by the automatic frequency planning process when the interference matrix scope inter- sects the automatic frequency planning scope.
12.8.7 get_Active
Returns the active state.
Parameters
[out] pIsActiveVal : Address of the VARIANT_BOOL used to return the active state of the interference matrix.
Remarks
An active interference matrix is used by the automatic frequency planning process when the interference matrix scope inter- sects the automatic frequency planning scope.
12.8.8 get_Type
Returrns the interference matrix type.
Parameters
[out] pImTypeVal : Address of the enumeration value used to return the interference matrix type.
Remarks:
Available enumeration values used to specify an interference matrix type are: 1 : PROPAG_IM
For interference matrices based on propagation data. Their reliability depends on the accuracy and correctness of network and geogrpahical data.
2 : OMC_RESELCTION_IM
For interference matrices based on reselection statistics from the OMC. Their reliability is usually low due to the difference between the locations where mobiles are switched on and where they are actually used to access the network.
3 : OMC_SIMPLE_HO_IM
Their reliability is usually low due to the fact that interference is measured only among existing neighbours, which might not be correctly assigned. This type of interference matrix is highly correlated with the neighbour relations. It can be used to
HRESULT put_Active( VARIANT_BOOL isActiveVal);
HRESULT get_Active(VARIANT_BOOL *pIsActiveVal);
Atoll 3.3.2 Task Automation Guide
Chapter 12: ChildFolder Feature Objects © 2016 Forsk. All Rights Reserved.
reason for low reliability is that interference information is collected from handover regions only, instead of from the service area.
4 : OMC_NEI_EXT_HO_IM
Interference matrices based on RXLEV statistics from the OMC (neighbours, as well as temporary neighbours).
They can be a very good source of interference information if they are statistically stable because they are not sensitive to data errors. On the other hand, they have many disadvantages, such as:
Transmitters with the same BSIC and BCCH cannot be differentiated. Transmitters having the same BCCH will never have an interference entry. Information is lost when more than 6 interferers exist at any location.
If many interferers share the same BCCH, they increase each other’s interference levels.
HCS layers can cause problems because there are more servers at any point, macro layer servers are stronger, or a correction margin might be introduced for some equipment.
This type of interference matrix can be created using an extended neighbours list. 5 : TEST_MOBILE_DATA_IM
Interference matrices based on test mobile data.
Reliability can be low because usually the test mobile data sampling zone and the traffic model are not related. Secondly, the measurements are carried out for existing neighbours only.
6 : CW_IM
Interference matrices based on CW measurements.
Their reliability can be low because the measurements usually do not reflect the traffic model. However, this source of infor- mation can be very reliable for a subset of transmitters that were properly scanned. Carrying out CW measurements is expen- sive which means that the collected information is often partial or out of date.
7 : SCAN_DATA_IM
Interference matrices based on scan data drive tests.
They are highly reliable and an excellent source of information, but are not useful in a radio planning tool because no infor- mation is available to map transmitters to the received signals at any pixel.
8 : UPPER_BOUND_ENTRY_COLLECTION Upper bound interference matrix.
The source of this type of interference matrix is not defined. It can be based on user experience. The information contained in this interference matrix is used as an upper limit, i.e., if this interference matrix indicates a certain level of interference, it should not be exceeded because other interference matrices show higher interference. If an upper bound interference matrix does not contain information about an entry, it is ignored.
9 : LOWER_BOUND_ENTRY_COLLECTION Lower bound interference matrix.
The source of this type of interference matrix is not defined. It can be based on user experience. The information contained in this interference matrix is used as a lower limit. This type of interference matrix can be very useful because you can edit entries in this interference matrix, and be certain that the interference will be at least as high as the value you entered. This approach can be used when user experience shows a certain level of interference which the radio network planning tool is unable to calculate.
12.8.9 put_Type
Sets the interference matrix type.
Parameters
[in] imTypeVal : The enumeration value used to specify the interference matrix type.
12.8.10 get_BasedOnTraffic
Returns based on traffic.
Parameters
[out] pbBasedOntraf: The address of the VARIANT_BOOL value used to return based on traffic.
Remark
This method only makes sense for interference matrices of type PROPAG_IM. In that case, the return value indicates whether the interference matrix takes into account non uniform traffic distributions within each cell.
12.8.11 put_BasedOnTraffic
Sets based on traffic.
Parameters
[in] bBasedOntraf : The VARIANT_BOOL value used to specify based on traffic.
12.8.12 get_Resolution
Returns the resolution of the interference matrix calculation.
Parameters
[out] piResolutionParamVal : The address of the long integer used to return the resolution of the interference matrix calcula- tion.
Remarks
For interference matrices of type PROPAG_IM, the return value is the resolution of the interference matrix calculation. For interference matrices of type TEST_MOBILE_DATA_IM, CW_IM, or SCAN_DATA_IM, the return value is the number of measurements per calculation point in the interference matrix.
12.8.13 put_Resolution
Sets the resolution of the interference matrix calculation.
Parameters
[in] :iResolutionParamVal : The long integer used to specify the resolution of the interference matrix calculation.
12.8.14 get_StdDev
Returns the interference matrix standard deviation.
Parameters
[out] pfStdDevParamVal: Address of the single precision floating point value used to return the interference matrix standard deviation.
HRESULT get_BasedOnTraffic(VARIANT_BOOL *pbBasedOntraf) ;
HRESULT put_BasedOnTraffic(VARIANT_BOOL bBasedOntraf) ;
HRESULT get_Resolution(long *piResolutionParamVal);
HRESULT put_Resolution(long iResolutionParamVal) ;
Atoll 3.3.2 Task Automation Guide
Chapter 12: ChildFolder Feature Objects © 2016 Forsk. All Rights Reserved.
Remarks
For interference matrices of type PROPAG_IM, the return value is the standard deviation of the propagation model used in the interference matrix calculation.
For interference matrices of type TEST_MOBILE_DATA_IM, CW_IM, or SCAN_DATA_IM, the return value is the standard devi- ation of the measurement equipment.
12.8.15 put_StdDev
Sets the interference matrix standard deviation.
Parameters
[in] fStdDevParamVal: The single precision floating point value used to specify the interference matrix standard deviation.
12.8.16 get_InfoQuantityIndicator
Returns the information quantity indicator.
Parameters
[out] pilInfoQuantIndic: Address of the long integer used to return the information quantity indicator.
Remarks
For interference matrices of type PROPAG_IM, the return value is an information about the interference matrix calculation parameters.
For interference matrices of type TEST_MOBILE_DATA_IM, CW_IM, or SCAN_DATA_IM, the return value is the number of calculation points per victim.
For interference matrices of type OMC_RESELCTION_IM, OMC_SIMPLE_HO_IM, or OMC_NEI_EXT_HO_IM, the return value is the number of days since the OMC statistics were collected.
12.8.17 put_InfoQuantityIndicator
Sets the information quantity indicator.
Parameters
[in] ilInfoQuantIndic : The long integer used to specify the information quantity indicator.
12.8.18 get_CdfTab
Returns the interference matrix CDF tabular data.
Parameters
[out] ppTable : Address of the ITabularData interface pointer used to return the inteference matrix tabular data.
Remarks
The structure of the Tabular Data object returned is: Column 1 : Row identifier of the victim transmitter
HRESULT put_StdDev(float fStdDevParamVal);
HRESULT get_InfoQuantityIndicator(long *piInfoQuantIndic);
HRESULT put_InfoQuantityIndicator(long iInfoQuantIndic) ;
Column 2 : Row identifier of the interferer transmitter Column 3 : A maximum loss value
Column 4 :
A safe array of type VT_ARRAY|VT_R4, VT_ARRAY|VT_R8, or VT_VARIANT having 1 dimension and containing the C/I values of the CDF.
Column 5 :
A safe array of type VT_ARRAY|VT_R4, or VT_ARRAY|VT_R8, or VT_VARIANT having 1 dimension and containing the proba- bility values of the CDF.
Performance considerations:
When deleting elements, try to always delete the last element first. When editing an existing element, do not change columns 1, 2, or 3.
Atoll 3.3.2 Task Automation Guide
Chapter 13
Document
Commands
Atoll 3.3.2 Task Automation Guide
13 Document Commands
The Atoll API enables executing commands on Atoll documents.
Commands are invoked by their names, which must be known in advance. The following commands are available for all Atoll documents:
The following commands are available for radio network technology documents:
Name Description Attributes
IMPORTXML This command performs the same task as the Atoll "File > Data Exchange > XML File Import..." main menu command.
Version: 2.7.1 EXPORTXML This command performs the same task as the Atoll "File > Data
Exchange > XML File Export..." main menu command.
Version: 2.7.0 APPENDTABLECOLUMN
This command adds a new column to a database table. This command is only available for Atoll documents that are not connected to
databases.
Version: 2.8.0
Name Description Attributes
CALCULATEPOINTS This command returns signal levels in dBm for a given set of points and a set of transmitters.
Version: 2.6.0 IMPORTTESTMOBILEDATA This command imports a set of drive test data files into an Atoll
document.
Version: 2.6.1
RUNNEIGHBOURALLOCATION Performs neighbour allocation on a GSM network. Version:
2.6.1 RUNINTERTECHNOLOGYNEIGHBOU
RALLOCATION
Performs inter technology neighbour allocation on a GSM or UMTS network.
Version: 2.6.1 RUNINTRACARRIERNEIGHBOURALL
OCATION Performs intra carrier neighbour allocation on a UMTS network.
Version: 2.6.1 RUNINTERCARRIERNEIGHBOURALL
OCATION Performs inter carrier neighbour allocation on a UMTS network.
Version: 2.6.1
CLONESTUDY This command clones a coverage prediction. Version:
2.7.0
DUPLICATESTUDY This command duplicates a coverage prediction. Version:
2.7.0
COMPARESTUDY This command compares two coverage predictions. Version:
2.7.0 CALCULATEEQUIPMENTLOSSES This command calculates equipment losses and noise figure for all
transmitters in the document transmitters folder.
Version: 2.7.0 CALCULATEREPEATERS This command calculates propagation losses, azimuth, mechanical tilt,
or gains for all repeaters in the document transmitters folder.
Version: 2.7.0 CALCULATEREMOTEANTENNAS This command calculates propagation losses, azimuth, mechanical tilt,
or gains for all remote antennas in the document transmitters folder.
Version: 2.7.0
EXPORTACTIVESETANALYSIS This command exports the active set analysis to text files. Version:
2.7.0 CALCULATEPOINTSECI0 This command returns Ec/I0 values in dB for a given set of points and a
set of transmitters. Version: 2.7.0
Atoll 3.3.2 Task Automation Guide
Chapter 13: Document Commands © 2016 Forsk. All Rights Reserved.
Input Parameters
Commands may have input parameters. The types and names of input parameters are unique and are specific to each command. PropertyContainer objects are used to hold input parameters.
Results
Commands may return results. Results are specific to each command. The results of a command are returned using a Proper- tyContainer object. Each result has a unique name and an associated type.