Professional Documents
Culture Documents
Opt 11 Interference Matrix Principles
Opt 11 Interference Matrix Principles
dn03516724 Issue 1
Nokia Oyj
1 (24)
Contents
The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This document is intended for the use of Nokia's customers only for the purposes of the agreement under which the document is submitted, and no part of it may be reproduced or transmitted in any form or means without the prior written permission of Nokia. The document has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this document concerning the suitability, capacity, or performance of the mentioned hardware or software products cannot be considered binding but shall be defined in the agreement made between Nokia and the customer. However, Nokia has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia will, if necessary, explain issues which may not be covered by the document. Nokia's liability for any errors in the document is limited to the documentary correction of errors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use of this document or the information in it. This document and the product it describes are considered protected by copyright according to the applicable laws. NOKIA logo is a registered trademark of Nokia Oyj. Other product names mentioned in this document may be trademarks of their respective companies, and they are mentioned for identification purposes only. Copyright Nokia Oyj 2003. All rights reserved.
dn03516724 Issue 1
2 (24)
Contents
Contents
1 1.1 1.1.1 1.1.2 1.1.3 2 3 3.1 3.2 3.3 3.4 3.5 3.6 3.7 4 About this document .............................................................................4 Where to find more...................................................................................4 Optimizer documentation .........................................................................4 Geographic Information System documentation ......................................4 Radio Access Configurator documentation ..............................................5 About interference matrix generation ..................................................6 Interference measurements ..................................................................7 Measurements needed for Optimizer .......................................................7 Channel Finder and Defined Adjacent Cell measurements .....................8 BCCH Allocation (BA) lists .....................................................................10 BCCH frequencies and Optimizer ..........................................................11 Identifying measured cells correctly .......................................................12 Measurement period ..............................................................................13 Measurements and NetAct capacity.......................................................14 Generating interference matrix elements for cells using the same BCCH as carrier..........................................................................15 Interference matrix options in Optimizer ...........................................16 Default interference matrix creation .......................................................16 Parameters affecting blind spot treatment..............................................17 Interference probability formulas .......................................................20 Average Received Power (ARP) ............................................................20 Carrier over Interferer Probability (CIP)..................................................22
dn03516724 Issue 1
3 (24)
1
1.1
1.1.1
Optimizer documentation
For information on the process of optimising a network using Optimizer, see Optimising a Network Using Optimizer. For detailed technical information on Optimizer, see Optimizer Technical Reference Guide. For information on Optimizer database tables, refer to Database Description for Optimizer. For detailed instructions on how to use the Optimizer applications, see the following helps:
1.1.2
For information on the Geographic Information System, see the following documents:
dn03516724 Issue 1
4 (24)
1.1.3
For information on the Radio Access Configurator, see the following documents:
Radio Access Configurator Principles Radio Access Configurator Technical Reference Guide
dn03516724 Issue 1
5 (24)
dn03516724 Issue 1
6 (24)
Interference measurements
Interference measurements
Optimizer uses measurement reports created by the Reporter module of NetAct. When the measurements are ready, measurement data can be retrieved from Reporter to Optimizer via Optimizers main user interface. BSC S10 provides the measurements that are needed for mobile measurement based optimisation of adjacencies and frequencies of the network. Nokia NetAct contains the support for the whole automated planning process, and it uses the BSC measurements as well as the network configuration database as inputs to the optimisation logic. The measurements used are Channel Finder Measurement in release S9 and Defined Adjacent Cell Measurement, new in S10. Both measurements are optional in BSC and available for Optimizer. The Radio Access Configurator (RAC) module of NetAct is also needed in order to manage Nokia BSS elements. Optimizer uses the functionality of RAC to get the actual network configuration. In addition to the interference matrix, also traffic data is utilised when a new frequency plan is computed. The interference matrix contains a quantitative description of interference relation and is not weighted with traffic. However, traffic measurements are taken into account in the cost function of the Frequency Allocation tool. The interference matrix can also be exported to be used with a preferred external AFP tool. Other relevant factors are taken into account by changing the parameter settings of the Frequency Allocation cost function.
3.1
Handover performance, for deleting unnecessary adjacencies (Handover Measurement). Defined Adjacent Cell measurement and Channel Finder measurement, for interference and missing adjacencies (Def. Adj. Cell Measurement and Channel Finder Measurement).
dn03516724 Issue 1
7 (24)
Interference measurements
There is also an Undefined Adjacent Cell measurement (Undef. Adj. Cell Measurement), which is very similar to the Channel Finder Measurement. The Channel Finder Measurement is, however, much more useful than the Undefined Adjacent Cell measurement.
For details on these measurements, see reference documentation for S10.5. The measurement scope and measurement period are defined in the Administration of Measurements application in NetAct. The measurements are activated per BSC, and all the BTSs in a BSC collect the information. For more information on this, see Administration of Measurements Help. Defined Adjacent Cell measurement and Channel Finder measurement should be started simultaneously and with the same measurement period.
3.2
average strength of the downlink signal BSIC+BCCH sum of the squares of the signal strengths (for standard deviation calculation) three sample counters for C/I values denominator of the average strength of the downlink signal received from the serving cell.
dn03516724 Issue 1
8 (24)
Interference measurements
For more information on the documentation of the counters with an example table and an explanation of the table fields, see BSC Counters: General Information on Measurements and Observations in S10 reference documentation.
BSC counters: Channel Finder Measurement
The channel finder measurement registers statistics on cells which have not been defined as adjacent cells but which are among those six neighbouring cells that the MS (mobile station) receives best. This measurement type collects one block of results for each cell. One block (cell) of results contains six counters:
Average strength of the downlink signal BCCH + BSIC Standard deviation (sum of squares of signal strengths) Three sample counters
BSC divides I/C values into intervals BSC measurements count values into I/C (=ICR) intervals instead of C/I (=CIR) intervals. This has an effect on how formulas are written and also on the software itself. The following table summarises how the BSC allocates each sample to one of the three ICR intervals defined by boundaries DB1 and DB2. ICR is used to assign each measurement to the corresponding interval. It is obtained from the BSC. CIR is easier to undestand; therefore, the meaning of counters n1, n2 and n3 in the table has been translated to CIR format.
n1
n2
n3
ICR CIR
DB1 <= ICR <= DB2 -DB2 <= CIR <= -DB1
The interval threshold between n1 and n2 is termed DB1. Its value may be for example -9 dB. The interval threshold between n2 and n3 is termed DB2 and its value may be for example 8 dB.
dn03516724 Issue 1
9 (24)
Interference measurements
3.3
With the Double BCCH Allocation List feature the user can define a list of BCCH carriers to be used in cell selection and reselection by the MS being in the Idle State. The list is sent to the MS in System Information Message type 2 on the BCCH and the MS may store it when powering down. Now, the MS does not need to search through the whole band when powering up. If the list contains all the BCCH carriers of a certain geographical area of a PLMN, the MS can use it to search the suitable RF channels quickly in order to camp on a cell. The BSC operator is able to add, remove and output carrier frequency numbers on the Idle State BCCH Allocation lists with the MML commands. For a particular cell it is possible to define whether it uses one of the Idle State Lists
dn03516724 Issue 1
10 (24)
Interference measurements
or the Neighbour Cell List of its own at System Information Message 2 on BCCH. If the cell is not attached to any of the Idle State Lists, the Neighbour Cell List is used as a default list. The frequency of the BCCH carrier of the cell itself is always added to the BCCH allocation in System Information message 2. Another selection can be made concerning the list in System Information Message 5 on SACCH. The default is the Neighbour Cell List, but if an Idle State List is attached to the cell to be used in System Information Message 2, the same list can also be used in System Information Message 5 on SACCH. If one of the Idle State Lists is selected to be used on SACCH, it is possible that the list contains carrier frequencies that are not the BCCH frequencies of the actual handover neighbours. In this case, the MS measures signals on these frequencies but no handovers are attempted towards those undefined cells. With the commands of the BCCH and Mobile Allocation Frequency List Handling (BAZAAR) command group, the user can create, modify, delete and output BCCH frequency list objects in the BSS Radio Network Configuration database (BSDATA). The user can attach any of these lists to certain BTSs with the commands of the command group Base Transceiver Station Handling (PBTHAN). The Double BCCH Allocation List is an optional feature in the BSC. For more information, see Radio Network Configuration Management.
Activating and testing BSS2132: Double BCCH Allocation List Deactivating and testing BSS2132: Double BCCH Allocation List
3.4
dn03516724 Issue 1
11 (24)
Interference measurements
3.5
dn03516724 Issue 1
12 (24)
Interference measurements
Figure 1.
Example of short distances between cells using an identical BCCH-BSIC combination causing the wrong cell to be measured
3.6
Measurement period
Optimizer requires measurements from a longer period (about one week), so that the measurements have to be scheduled for some hours for several days. The measurements are sent from the BSC to Reporter after each day. Running measurements for a long time causes extra load to the network and also to the MS handover behaviour. For identifying unnecessary adjacencies, measurements can be done during several days. When toggling the BCCH band and measuring received signals, the list of correct adjacencies can be generated by measuring for a couple of hours (3-4 hours) during a few days (2-3 days). The required time depends on the traffic profile in the network.
dn03516724 Issue 1
13 (24)
Interference measurements
3.7
dn03516724 Issue 1
14 (24)
Generating interference matrix elements for cells using the same BCCH as carrier
Generating interference matrix elements for cells using the same BCCH as carrier
While in measuring mode, mobiles measure the power level of as many BCCH carriers as is listed in the BA list, and decode their BSIC in order to determine the cell emitting the signal. Any cells having the same BCCH with the serving cell are generally not measured. This is because the serving cell signal is usually much stronger and covers all other signals on the same frequency. These cochannel cases are seen as blind spots in the interference matrix. Even though the measurements show no or a very small value for these co-channel BCCH cell pairs in the interference matrix, some of these pairs may in reality interfere with each other. Therefore, a method is introduced in Optimizer to avoid missing these blind spot interference relations. This method is described in the following section.
dn03516724 Issue 1
15 (24)
The InterferenceOptions.xml is not in the above-mentioned directory by default. It appears after the first measurement retrieval.
5.1
4.
dn03516724 Issue 1
16 (24)
5.
Finally, the new interference matrix is saved into the Optimizer database.
This default procedure can be altered by changing the interference matrix options. Two of the options (Population Method and Penalty Method) can be changed in the user interface or in the InterferenceOptions.xml file. Other options can be changed only in the above-mentioned file.
5.2
Keep Blind Spots Only This is the default value. Blind spots are recognised in the actual allocation. A new interference matrix is calculated based on the new measurements, but data into the blind spots is acquired from the old interference matrix. Overload A new interference matrix is calculated based on new measurements and it is loaded on top of the old matrix. Where data source cells overlap, new data replaces the old data. However, where no new data exists, old data remains.
Instructions for setting the population method are given in the Optimizer Main User Interface Help.
Penalty method
The penalty method can be set in the Optimizer main user interface. The options are:
Distance Only Only distance is used in interferer recognition and in sorting BTSs in blind spots. Use this method only if antenna azimuths are not available. Distance and Antenna Bearing Both distance and antenna bearing are used in interferer recognition and also in sorting BTSs in blind spots. This is the recommended method.
Instructions for setting the penalty method are given in the Optimizer Main User Interface Help.
Blind spot limitation method
The blind spot limitation method can only be set in the InterferenceOptions.xml file.
Enumeration name
Explanation
dn03516724 Issue 1
17 (24)
LIST_LENGTH_LIMITED
The number of blind spots per BTS is limited by a list length limit. The name of this limit is blindSpotListLengthLimit. This is the default value of the blindSpotLimitationMethod. The number of blind spots per BTS is limited by the distance of BTSs from each others. This distance is given in the parameter blindSpotDistanceLimit. Interference relations are created into all new blind spots. No new interference relations are created even if there are blind spots between BTSs.
DISTANCE_LIMITED
TAKE_ALL NO_NEW_BLIND_SPOTS
Table 2.
Method for selecting BTSs in blind spots for automatic interference creation into interference matrix (blindSpotLimitationMethod)
Other options and parameters The parameters and options described in the table below can only be set in the InterferenceOptions.xml file.
Name blindSpotListLengthLimit
Explanation
Default value
Min 0
Max 50
Unit -
Used to restrict the number of 3 BTSs to be assigned a default interference value (ARP or CIP), if this limitation is used. Used to restrict the number of 20 BTSs to be assigned a default interference value (ARP or CIP), if this limitation is used. Default interference value (ARP) 1 that is put into blind spot if there is no value previously. Default interference value (CIP) 0.05 that is put into blind spot if there is no value previously. Used to define the difference between co-channel ARP and adjacent channel ARP values. 18
blindSpotDistanceLimit
70
km
blindSpotCoARP
63
RXLEV
blindSpotCoCIP
0.0
1.0
coAdjDifferenceARP
63
dB
dn03516724 Issue 1
18 (24)
Table 3.
dn03516724 Issue 1
19 (24)
6.1
Figure 2.
where
dn03516724 Issue 1
20 (24)
Pi,j = Average RXLEV measured from cell j by mobiles served by cell i (average counted only over such reports where cell j is included). Ni,j = The number of such mobile measurement reports received by cell i, where cell j has been included, Therefore, Pi,j*Ni,j is simply the sum of RXLEV samples from cell j to cell i. Mi = The number of all mobile measurement reports received by cell i, no matter if cell j is included in the report or not. nki,j = The number of such mobile measurement reports received by cell i where cell j is included and where RXLEVj - RXLEVi belongs to interval k. BSC classifies each sample to these I/C intervals. For details, see BSC S10.5 specifications.
The RXLEV value interval of ARP is [0.0, 63.0] although in practice the values are likely to be from the lower side of the scale. This is because measurement samples are from all over the cell i service area, and it is thus unlikely that any one cell would be measured all over that area (co-located 1800 cells may be exceptions). Received signal strength Pi,j and ARP (GSM 05.08; 8.1.4) mean the following values:
0 less than -110 dBm 1 = -110 to -109 dBm 2 = -109 to -108 dBm ... 62 = -49 to -48 dBm 63 = greater than -48 dBm
In allocation, also adjacent channel interference should be treated. With ARP the computation can be made as follows:
Figure 3.
where
dn03516724 Issue 1
21 (24)
ARPi,jco = Average Received Power for co-channel, equal to ARPi,j defined in the equation for ARP where a shorter notation was used for convenience.
The logic in estimating the adjacent frequency interference from co-frequency interference is that the GSM specifications define that interference leaking from adjacent GSM frequency should be at least 18 dB lower than interference in the same conditions from the same GSM frequency.
6.2
Figure 4.
where
CIPi,jco = Estimated interference from cell j to cell i on the same frequency. n2i,j = the number of samples from cell j to cell i in CIR category n2. n3i,j = number of samples from cell j to cell i in CIR category n3. Mi = The number of all mobile measurement reports received by cell i, no matter if cell j is included in the report or not.
Similarly, CIPadj (or C/Ia(%)) is computed from measurement reports with the following formula:
dn03516724 Issue 1
22 (24)
Figure 5.
where
CIPi,jadj = Estimated interference from cell j to cell i on an adjacent frequency. n3i,j = number of samples from cell j to cell i in CIR category n3. Mi = The number of all mobile measurement reports received by cell i, no matter if cell j is included in the report or not.
CIP values are represented as floating point numbers with four number accuracy (two decimals). The interval is [0.01,100.0] and unit percentage (%). Note that CIP estimates the portion of time which any call receives weaker CIR than a given threshold. Usually about 9 dB is considered as a good threshold for good quality call. When setting parameters DB1 and DB2 in BSCs, note that BSC uses ICR and not CIR when allocating each sample to a corresponding interval (n1, n2 or n3). Therefore, if CIPi,jco is wanted to represent probability to have weaker than or equal to 9 dB CIR, then DB1 should be set to -9 dB in the BSC. Note that the value of DB2 does not affect to value of CIPi,jco . If 10 dB CIR is acceptable for co-channel and 18 dB attenuation from adjacent channel is assumed, then CIR of -8 is acceptable for adjacent frequency. Therefore, DB2 should be set to +8 dB in the BSC.
dn03516724 Issue 1
23 (24)
Index
Index
interference matrix options, 16
A
ARP, 6, 20 Average Received Power, 6, 20
M
measurement period, 13 measurement report, 7 Measurement source dialog, 12
B
BA list, 10, 14 BCCH Allocation list, 10 blind spot, 17 BSC counter, 8 BSIC, 12
N
NetAct, 14
R C
Carrier over Interferer Probability, 6, 22 CIP, 6, 20 Radio Access Configurator, 7 Reporter, 7 RXLEV, 20
D
Double BCCH Allocation list, 10
T
traffic data, 7
I
interference matrix, 6
dn03516724 Issue 1
24 (24)