Professional Documents
Culture Documents
Page 57
A description of the *.ait file format can be found in the ENTERPRISE Technical Reference Guide.
The new interference table is loaded into memory, replacing the previous table.
If a table already exists in memory and you want to merge the tables
1 2 From the Tools menu, point to Interference Tables and click Load Interference Table. Select the file (*.ait) that you want to load and click Open. A 'merge/replace' message prompt appears. 3 Click 'Yes'. The following dialog box appears, enabling you to select merging options:
Page 59
Where there are 'victim' cells in the new table that are not present in the existing table, you can select this option to append them. If you do not select this option, the newly imported data will only be merged for the existing 'victim' cells (this may be useful if you want to update the table for a specific group of victim cells only, but using newly imported data from a large file).
If you are merging newly imported traffic-only data with area-only data (or vice versa), then the percentage options are inactive because all the new values will be imported, without any need for weighting. 5 Click Apply.
The data in the imported table is merged with the data in the existing table, according to your specified options, and an updated interference table is loaded into memory.
The 'Interferer' column of the file can either contain the BCCH_BSIC combination for the cell (for example, Unknown/38_07), or the cell identity (for example, BSC1/Site7A). For the BCCH_BSIC option, to identify the interfering cell in the project, ASSET searches the map data within a specific radius* of the 'victim' cell for the nearest instance of the BCCH_BSIC combination. (The radius is either the Primary Prediction Radius for the cell in the Site Database, or 10km, whichever is the higher.) For the Cell ID option, to identify the interfering cell in the project, ASSET finds the cell directly in the Site Database. However, if your Site Database configuration includes some cells that contain more than one cell layer, there may be a problem finding the correct sub-cell. For this reason, a drop-down list in the loading dialog box enables you to determine which cell layer should be used for the interference table. If the sites and cells in your project are configured (as recommended) so that one cell always only contains one cell layer, then this drop-down list is insignificant.
Page 60 ASSET 6.2 New Features Training Notes Version 6.2
(This message prompt does not appear if there is no table already in memory.) Click 'Yes' or 'No', as appropriate. 4 The next dialog box that appears enables you to select loading and merging options:
Page 61
From the drop-down list, select the cell layer to be used for the interference table, in the case where cell identities in the .msmt file relate to cells containing multiple cell layers. This cell layer drop-down list is significant only if: Your Site Database configuration includes some cells that contain more than one cell layer - and The 'Interferer' column of your *.msmt file contains instances of cell identities (for example, BSC1/Site7A), rather than the BCCH_BSIC combination
If the sites and cells in your project are configured (as recommended) so that one cell always only contains one cell layer, then this drop-down list is insignificant. 6 Where applicable, specify the data merging options, as described in this table: These options are only active if there was already an interference table in memory, and you chose 'Yes' to merge the new data.
Option Imported values weight (%) Description If you are merging a new table with an existing table, there will probably be interferer relations that exist in both tables. So you must specify a percentage to determine the proportional weight of the newly imported values against the existing values. For example, if you specify 70% here for the imported values, there will be a 30% weight for the existing values. (Orders of scale are used to match the total traffic values in each table.) Apply 100% Where there are interferer relations in the new table that do not exist at all in the existing table, you weighting to missing can select this option to add the imported values with a 100% weighting. interferer relations If you do not select this option, the weighting specified in the imported values weight box will be used. Append extra 'victim' server measurements Where there are 'victim' cells in the new table that are not present in the existing table, you can select this option to append them. If you de-select this option, the newly imported data will only be merged for the existing 'victim' cells (this may be useful if you want to update the table for a specific group of victim cells only, but using newly imported data from a large file).
If you are merging newly imported traffic data (from the *.msmt file) with area-only data (from the existing *.ait file), then this percentage option is inactive because all traffic values will be imported, without any need for weighting. 7 Click Apply.
The new table (merged or otherwise) is automatically post-processed into the *.ait file format, and loaded into memory.
Page 62
Click Next.
Page 63
Set the interference parameters and traffic options. You can: Select one or more interfering cell layers. Choose to consider interference between different cell layers. Set an adjacent channel offset. Set a Maximum Relative Rx Level Margin. A cell can only be considered as an interferer if the signal difference is less than or equal to this value. Select which traffic arrays to include, if required (only available if one or more arrays exist in memory). Select the interference probability method. See How Probability of Interference is Calculated.
Click Next. 7 You can choose to save the generated interference table to an *.ait file (or you can save it later). You can also select whether you want to view the table after running the wizard (or you can view it later), and you can add any comments. Click Next. 8 Check the summary and click Finish.
The interference table is created, and according to your choices in the wizard, saved and displayed. The interference table is based on the project parameters and (if applicable) traffic data at the time of running the wizard. In certain circumstances, if the parameters or data have changed, you may want to generate a new up-to-date Interference Table. In other words, the 'validity' of the Interference Table is under user-control.
Page 64