1 Nokia Siemens Networks RF hopping workshop / 19.01.2009.
RF Hopping Workshop (Nokia)
2 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Table of content Introduction Functionality Reuse and load calculations Planning and planning cases Parameters Measurements Feature interworking BTS configurations Activating RF hopping
3 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Introduction Network capacity Frequency hopping basics and hopping gain Power control and DTX
4 Nokia Siemens Networks RF hopping workshop / 19.01.2009. CAPACITY GAIN Effective Network Planning Channel-Bandwidth Spectrum Cell Size Reuse-Factor (C/I) Dual-Band-/ Dual-Mode- Networks PC DTX Smart Antennas Hopping Half-Rate Networks Antenna arrangement Micro cell Pico cell / Indoor Network Capacity 5 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Frequency Time F 1 F 2 F 3 Call is transmitted through several frequencies in order to minimize the impact of fading (frequency diversity) average the interference (interference diversity) What is Frequency Hopping? Frequency hopping can be briefly defined as a sequential change of carrier frequency on the radio link between the mobile and the base station. 6 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Signal Level Distance MS Location F 3 F 2 F 1 Bursts sent on frequency F2 are degraded or lost, but the initial signal may still be reconstructed from the bursts on frequencies F1 and F3. Frequency diversity Fast fading Compensates the frequency selective fast fading Mobile station Base station 7 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Frequency diversity Coherence Bandwidth Performance Dependency Coherence bandwidth represents a bandwidth that is required between two frequencies in order to ensure that their fading characteristics are different enough to provide properly uncorrelated amplitudes and phases. The coherence bandwidth depends strongly on the mean delay spread of the environment. The delay spread is defined as the standard deviation of the mean delay time. The measurements indicate that the delay spread is highly dependent on the environment.
In open and indoor environments: Short Delay Spread High Coherence Bandwidth More frequency spacing required
Type of environment Delay spread A, s Open area < 0.2 Suburban area 0.5 Urban area 3 8 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Frequency diversity Channel separation The autocorrelation coefficient has been plotted for several different values of delay spread. The urban environment even the adjacent channel having separation of 200 kHz appears to be adequately uncorrelated In the suburban environment the channel separation of 400 kHz is adequate. In open environment the channel separation should be at least 800 kHz corresponding to four GSM carriers. 0.0 0.1 0.2 0.3 0.4 0.5 0.6 0.7 0.8 0.9 1.0 0 1 0 0 2 0 0 3 0 0 4 0 0 5 0 0 6 0 0 7 0 0 8 0 0 9 0 0 1 0 0 0 1 1 0 0 1 2 0 0 1 3 0 0 1 4 0 0 1 5 0 0 frequency spacing (kHz) a u t o c o r r e l a t i o n
c o e f f i c i e n t 0.2 0.5 1 2 3 delay spread (s) f 1 f 2 f 3 f 4 f 1 f 2 f 3 f 4 f 1 f 2 f 3 f 4 f 1 f 2 f 3 f 4 f 1 f 2 f 3 f 4 f 5 9 Nokia Siemens Networks RF hopping workshop / 19.01.2009. 0 1 2 3 4 5 6 7 8 0 1 2 3 4 5 6 7 8 Number of hopping frequencies G a i n
[ d B ]
Cyclic, TU3 Random, TU3 Cyclic, TU50 Random, TU50 Frequency Diversity Gain Relation to # of frequencies
A higher mobile speed alone provides a better performance against fast fading -> frequency diversity gain decreases -> the total gain remains the same 10 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Coverage Improvement (%) 0 5 10 15 20 1 2 3 4 5 6 7 8 Number of Frequencies (FH) Frequency Diversity Gain Coverage area improvement Hopping over 8 frequencies provides over 3 dB improvement BCCH timeslot in BB FH and BCCH TRX in RF FH doesnt hop -> an increased coverage area is limited by the coverage area of the non- hopping BCCH time slot or BCCH TRX
11 Nokia Siemens Networks RF hopping workshop / 19.01.2009. According to the simulations, the SDCCH channel gets a smaller frequency diversity gain than TCH channel => Call setups , SMSs affected
0.001 0.01 0.1 1 0 2 4 6 8 10 12 14 C/I F E R SACCH NH SACCH RH4 SACCH RH8 TCH NH TCH RH4 TCH RH8 Different Channel Coding Different Interleaving Different Hopping Gains
Frequency Hopping Gains TCH & SACCH 12 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Interference diversity In a conventional non-hopping network, each call is transmitted on a single fixed frequency, so the interference situation in a network is also quite stable. Some calls may experience very little interference and the other calls may be interfered severely. In random hopping network, the interference sources vary from burst to burst, thus the interference tends to get averaged over all the calls in the network. The interference affecting each call in the network has a lower standard deviation around its mean value. The probability of several consecutive corrupted bursts and erased frames decreases, because the severely interfered bursts occur randomly. 13 Nokia Siemens Networks RF hopping workshop / 19.01.2009. 0 0.2 0.4 0.6 0.8 1 1.2 1.4 1.6 1.8 2 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% Load G a i n
( d B ) 2 f requencies 3 f requencies 4 f requencies 8 f requencies 12 f requencies Poly. (2 f requencies) Poly. (4 f requencies) Poly. (3 f requencies) Poly. (8 f requencies) Poly. (12 f requencies) Interference Diversity Gain Simulated Results 14 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Field strenght Serving carrier average weakest interference average strongest interference interference margin worst interference FH with tighter frequency reuse FH with improved quality no FH C/I C I New margin Reuse 15 Converting Quality to Capacity
15 Nokia Siemens Networks RF hopping workshop / 19.01.2009. In reality, the gain of PC with high mobile speed can be even lower GAIN: PC on 1.4 dB DTX on 2.3 dB PC on, DTX on 3.7 dB GAIN: PC on 1.0 dB DTX on 2.3 dB PC on, DTX on 3.5 dB Reuse 3/9, TU 3km/h Reuse 3/9, TU 50km/h C/I improvement Effect of Power Control and DTX Downlink simulation Power Control and DTX give an additional capacity gain with random FH. Well documented in IEEE VTC2000 Comparison of Networks with different frequency reuses, DTX and Power Control using the effective Frequency Load Approach
17 Nokia Siemens Networks RF hopping workshop / 19.01.2009. MSC PSTN BB-FH F 1 (+ BCCH) F 2 F 3 Dig. RF TRX-3 TRX-1 RF-FH F 1 , F 2 ,
F 3 Dig. RF TRX-1 TRX-2 BSC TCSM BCCH Frequency Time F 1 F 2 F 3 MS does not see any difference BB-FH is feasible with large configurations RF-FH is viable with all configurations FH Implementation 18 Nokia Siemens Networks RF hopping workshop / 19.01.2009. BCCH 1 2 3 7 6 4 0 1 2 3 7 6 4 0 1 2 3 7 6 4 0 1 2 3 7 6 4 TRX-1 TRX-2 TRX-3 TRX-4 RTSL-0 RTSL-2 RTSL-1 RTSL-4 RTSL-3 RTSL-5 RTSL-6 RTSL-7 f1 f2 f3 f4 BCCH timeslot, does not hop. 5 5 5 5 Timeslot 0 of TRXs 2-4 hop over MA(f2,f3,f4). This hopping group uses HSN-1 All timeslots 1-7 hop over MA(f1,f2,f3,f4). This hopping group uses HSN-2 BB Hopping Management
19 Nokia Siemens Networks RF hopping workshop / 19.01.2009. BCCH 1 2 3 7 6 4 0 1 2 3 7 6 4 0 1 2 3 7 6 4 0 1 2 3 7 6 4 TRX-1 TRX-2 TRX-3 TRX-4 RTSL-0 RTSL-2 RTSL-1 RTSL-4 RTSL-3 RTSL-5 RTSL-6 RTSL-7 f1 BCCH TRX does not hop. 5 5 5 5 MAIOs are different for different TRXs within the same hopping group -> no collisions. MA1 = {f2, f3, f4,..} HSN-1 RF Hopping Management
20 Nokia Siemens Networks RF hopping workshop / 19.01.2009. FH functionality Cell Allocation (CA) It is a list of all the frequencies allocated to a cell. The CA is transmitted regularly on the BCCH and usually it is also included in the signaling messages Mobile Allocation (MA) The MA is a list of hopping frequencies transmitted to a mobile every time it is assigned to a hopping physical channel. The MA-list is a subset of the CA list. The MA-list is automatically generated if the baseband hopping is used. If the network utilizes the RF hopping, the MA-lists have to be generated for each cell by the network planner. The MA-list is able to point to 64 of the frequencies defined in the CA list. However, the BCCH frequency is also included in the CA list, so the practical maximum number of frequencies in the MA-list is 63. The frequencies in the MA-list are required to be in increasing order because of the type of signaling used to transfer the MA-list. 21 Nokia Siemens Networks RF hopping workshop / 19.01.2009. FH functionality Hopping Sequence Number (HSN) It indicates which hopping sequence of the 64 available is selected. The hopping sequence determines the order in which the frequencies in the MA-list are to be used. The HSN 0 is reserved for a sequential sequence used in the cyclic hopping. The HSNs 1 - 63 are pseudo random sequences used in the random hopping The HSN is a cell specific parameter. For the baseband hopping two HSNs exists. The TSL0s in a BB hopping cell use the HSN1 and the rest of the time slots follow the HSN2 All the time slots in RF hopping cell follow the HSN1
BCCH 1 2 3 7 6 4 0 1 2 3 7 6 4 0 1 2 3 7 6 4 0 1 2 3 7 6 4 TRX-1 TRX-2 TRX-3 TRX-4 RTSL-0 RTSL-2 RTSL-1 RTSL-4 RTSL-3 RTSL-5 RTSL-6 RTSL-7 f1 f2 f3 f4 BCCH timeslot, does not hop. BCCH timeslot, does not hop. 5 5 5 5 Timeslot 0 of TRXs 2-4 hop over MA(f2,f3,f4). This hopping group uses HSN-1 Timeslot 0 of TRXs 2-4 hop over MA(f2,f3,f4). This hopping group uses HSN-1 All timeslots 1-7 hop over MA(f1,f2,f3,f4). This hopping group uses HSN-2 All timeslots 1-7 hop over MA(f1,f2,f3,f4). This hopping group uses HSN-2 BCCH 1 2 3 7 6 4 0 1 2 3 7 6 4 0 1 2 3 7 6 4 0 1 2 3 7 6 4 TRX-1 TRX-2 TRX-3 TRX-4 RTSL-0 RTSL-2 RTSL-1 RTSL-4 RTSL-3 RTSL-5 RTSL-6 RTSL-7 f1 f2 f3 f4 BCCH timeslot, does not hop. BCCH timeslot, does not hop. 5 5 5 5 Timeslot 0 of TRXs 2-4 hop over MA(f2,f3,f4). This hopping group uses HSN-1 Timeslot 0 of TRXs 2-4 hop over MA(f2,f3,f4). This hopping group uses HSN-1 All timeslots 1-7 hop over MA(f1,f2,f3,f4). This hopping group uses HSN-2 All timeslots 1-7 hop over MA(f1,f2,f3,f4). This hopping group uses HSN-2 BCCH 1 2 3 7 6 4 0 1 2 3 7 6 4 0 1 2 3 7 6 4 0 1 2 3 7 6 4 TRX-1 TRX-2 TRX-3 TRX-4 RTSL-0 RTSL-2 RTSL-1 RTSL-4 RTSL-3 RTSL-5 RTSL-6 RTSL-7 f1 BCCH TRX does not hop. BCCH TRX does not hop. 5 5 5 5 MAIOs are different for different TRXs within the same hopping group -> no collisions. MAIOs are different for different TRXs within the same hopping group -> no collisions. MA1 = {f2, f3, f4,..} HSN-1 HSN-1 22 Nokia Siemens Networks RF hopping workshop / 19.01.2009. FH functionality Mobile Allocation Index Offset (MAIO) When there is more than one TRX in the BTS using the same MA-list the MAIO is used to ensure that each TRX uses always an unique frequency. Each hopping TRX is allocated to different MAIO. MAIO and HSN are transmitted to a mobile together with the MA-list. In Nokia solution the MAIOoffset is a cell specific parameter defining the MAIOTRX for the first hopping TRX in a cell. The MAIOs for the other hopping TRXs are automatically allocated according to the MAIOstep parameter MAIO is added to MAI when the frequency to be used is determined from the MA-list. MAIOstep It is a Nokia specific parameter used in the MAIO allocation to the TRXs. The MAIO for the first hopping TRXs in each cell is defined by the cell specific MAIOoffset parameter. MAIOs for the other hopping TRXs are assigned by adding the MAIOstep to the MAIO of the previous hopping TRX 23 Nokia Siemens Networks RF hopping workshop / 19.01.2009. MAIO assignment MAIO TRX:
Example: ) 1 ( ) ( + = n MAIO MAIO MAIO step offset n TRX DOCUMENTTYPE TypeUnitOrDepartmentHere TypeYourNameHere TypeDateHere Sector TRX # HSN MAIO stepMAIOoffsetl MAIO 1 1 Non-hopping BCCH TRX 2 7 2 0 0 3 2 4 4 2 1 Non-hopping BCCH TRX 2 7 2 6 6 3 8 4 10 3 1 Non-hopping BCCH TRX 2 7 2 12 12 3 14 4 16 MAIO step indicates the difference between the MAIOs of successive TRXs in a cell. +MAIO step 24 Nokia Siemens Networks RF hopping workshop / 19.01.2009. FH Sequence Generation with MAIO Mobile Allocation Index (MAI) The hopping sequence algorithm takes HSN and TDMA frame number (FN) as an input and the output of the hopping sequence generation is a Mobile Allocation Index (MAI) which is a number ranging from 0 to the number of frequencies in the MA-list subtracted by one.
DOCUMENTTYPE TypeUnitOrDepartmentHere TypeYourNameHere TypeDateHere GSM Hopping algorithm MAI (0...N-1) = f 1 f 2 f 3 f 4 f N f N-1 MA 0 1 2 3 N-1 N-2 MA INDEX (MAI) TRX-1 TRX-2 TRX-3 FN & HSN MAIO TRX TRX-1 0 TRX-2 1 TRX-3 2 For this TDMA frame the output from the algorithm is 1 1 1 + MAIO TRX 25 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Reuse and load calculations
Effective reuse Frequency Allocation Reuse Frequency load 26 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Effective reuse Since the frequency band is always limited, the frequencies have to be reused in the network. As the reuse distance becomes smaller, there are more frequencies available for each cell, so more capacity can be provided. The effective reuse is essentially the same as the conventional frequency reuse distance.
where: Reff = effective reuse NfreqsTOT = total number of used frequencies NTRXave = average number of TRXs in a cell
The smaller the effective reuse, the higher the capacity in terms of the number of TCHs provided by one frequency in the network. R N N eff freqsTOT TRXave = 27 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Frequency Allocation Reuse RF Hopping only Frequency allocation reuse indicates how closely the frequencies are actually reused in a network.
where: FAR = frequency allocation reuse NfreqsTOT = total number of used frequencies Nfreqs/MA = average number of frequencies in MA-lists
It indicates the severity of a worst case C/I in the cell border. If the network doesnt utilize fractional loading, the frequency allocation reuse is the same as the effective reuse. FAR N N freqsTOT freqs MA = / 28 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Frequency Allocation Reuse = Total # of frequencies / # of frequencies in MA list Effective Reuse = Total # of frequencies/ Number of TRXs per cell Effective Reuse = Frequency Allocation Reuse Total # of freqs = 30 4 TRXs / cell 10 frequencies / cell 3 2 1 1 1 2 2 3 3 1/3 FAR = 30/10 = 3 Eff.reuse = 30/4 =7.5 Example: Reuse in RF hopping networks 29 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Frequency load The C/I is low when frequency collisions occur. In order to guarantee an adequate quality, the collision probability has to be made low. The collision probability depends on the load of the hopping frequencies called a frequency load. The frequency load describes the probability that a frequency channel is used for transmission at one cell at one time. The frequency load is a product of two other loads: hard blocking load (the average busy hour TCH occupancy in most of the cases) fractional load
where: L freq = frequency load L HW = the busy hour average hard blocking load L frac = fractional load L L L freq HW frac = 30 Nokia Siemens Networks RF hopping workshop / 19.01.2009. L T N HW hopTCH hopTCH = Hard blocking load The hard blocking load is calculated as
where: L HW = hard blocking load T hopTCH = average number of used TCHs in the busy hour N hopTCH = total number of TCHs in the hopping TRXs
31 Nokia Siemens Networks RF hopping workshop / 19.01.2009.
BCCH SDCCH SDCCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TRX-1 TRX-2 TRX-3 TRX-4 f1 f2,f3,f4 f3,f4,f2 f4,f2,f3 TCH TCH TCH TCH Active slots Empty slots 75 % 25 % Load on the BCCH TRX not considered, since the BCCH frequencies are planned separately Hard blocking load
Hard blocking load = 18 / 24 = 0.75 32 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Fractional load Fractional load means that the cell has been allocated more frequencies than TRXs. This is only possible for RF hopping TRXs. The fractional load is very useful when the number of TRXs is low. By utilizing fractional load, it is possible to provide enough frequencies to hop over (to get FH gain) to even a cell with just one hopping TRX.
where: L frac = fractional load N TRX = number of TRXs in a cell N freqs/cell = number of frequencies allocated to a cell (MA-list length)
L N N frac TRX freqs cell = / 33 Nokia Siemens Networks RF hopping workshop / 19.01.2009. DOCUMENTTYPE TypeUnitOrDepartmentHere TypeYourNameHere TypeDateHere BCCH TRX-1 TRX-2 TRX-3 TRX-4 f1 f2, f3, f4, f5, f6 f2, f3, f4, f5, f6 f2, f3, f4, f5, f6 Active slots Empty slots Frac. load = 3/5 = 0.6 Fractional load 5 frequencies on 3 TRXs 34 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Frequency Load HW and fractional load BCCH 1 2 3 7 6 4 0 1 2 3 7 6 4 0 1 2 3 7 6 4 0 1 2 3 7 6 4 TRX-1 TRX-2 TRX-3 TRX-4 f1 f2, f3, f4, f5, f6 f3, f4, f5, f6, f2 f4, f5, f6, f2, f3 5 5 5 5 Active slots Empty slots HW load is 75% Fractional load FL is 3 TRX / 5 F = 0.6 = 60% Frequency load is HWL * FL = 45% 75 % 25 % (E)GPRS is on the BCCH layer in this case 35 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Effective Reuse and Frequency Allocation Reuse Relations Equation shows the fixed relation between the effective and frequency allocation reuses and the fractional load.
R N N N N N N FAR L eff freqsTOT TRX freqsTOT freqs MA freqs MA TRX frac = = = / / 36 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Hard blocking
The whole radio resource is in use - no more calls can be established due to lack of free radio timeslots.
Soft blocking
The capacity of individual cells is limited by the level of the interference rather than the number of TRXs available
Dominates with large reuse factors Is dominating with tight reuse patterns What is a feasible reuse? Hard/soft blocking 37 Nokia Siemens Networks RF hopping workshop / 19.01.2009. 12 (no hopping) 9 3 reference Erl/cell +31% +40% BLOCKING TYPE: Hard Hard Soft 1 +30% Soft CALL DROP RATE: 0% 0.2% 2% 2% Safe to implement in practice REUSE FACTOR: (Freq. Allocation reuse) 6 Soft 2% +33% Load control needed What is a feasible reuse? 38 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Planning Hopping strategy Frequency planning 39 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Flexibility hopping with small configurations and small BW is possible Maximum FH gain or easy allocation possible hopping enabled over large number of frequencies Number of antennas in large configurations the number of antennas increases HW dependencies old BTS generations do not support RF-FH wideband antenna coupling equipment needed (AFEs) BCCH TRX is included (TSL1-7) Less HW restrictions supported by all BTS generations and combiners minimum number of antennas required Easy to Implement (switch on) existing planning tools can be used Limitations with small configurations and small BW minimum of three TRXs in a cell should be used limited FH gain with small configurations (< 3 TRX / cell) Downlink PC range should be restricted to 10-14 dB
BB-FH RF-FH No simple answer, selection on case by case basis Hopping strategy BB-FH vs. RF-FH 40 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Hopping strategy Cyclic vs. Random Hopping Sequences Both cyclic and random hopping modes are available in GSM.
In the cyclic mode the frequencies are changed sequentially from the lowest frequency to the highest as defined in the MA-list. In random mode the frequency to be used for each burst is selected from the MA-list by a predefined pseudo random sequence. This means that the same frequency may be used for a couple of consecutive bursts and the frequencies are not used evenly in a short time scale.
As the number of frequencies becomes larger the difference between the cyclic and the random mode becomes small.
41 Nokia Siemens Networks RF hopping workshop / 19.01.2009. For both: Intracell HO to another timeslot always changes the interferers Cyclic: Optimum frequency diversity gain Interference diversity gain NOT optimum Risk of having one strong interferer to affect several consecutive bursts Random: Frequency diversity gain NOT optimum, especially with short MA lists Interference diversity gain optimum Hopping strategy Cyclic vs. Random Hopping Sequences 42 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Cyclic: In the areas where the interference is NOT a problem (low traffic areas, <= 3 TRXs) Random: In the areas where the interference is a problem (high traffic areas) and long MA lists can be used (or >= 4 TRXs with BB FH) Hopping strategy Cyclic vs. Random Hopping Sequences 43 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Frequency planning Frequency allocation strategies BCCH band allocation It must be decided whether to use a separate frequency band for the BCCH carriers or use a common band for both the BCCH and the normal TCH TRXs.
FAR vs. Frequency load When preparing for a frequency allocation, some decisions have to be made concerning the wanted frequency allocation reuse and the corresponding frequency load. 44 Nokia Siemens Networks RF hopping workshop / 19.01.2009. BCCH Planning Simulation results Setup 108 cells with 3,4 and 5 TRX/cells, 27 channels and same load on BCCH and TCH TRXs Common -> 27 frequencies (BCCH with reuse of 27, TCH was allocated by slow Adaptive Channel Allocation (ACA)) Dedicated -> 12 frequencies were dedicated to the BCCH TRXs and the remaining 15 frequencies were used as TCH frequencies (ACA) Mixed -> separated but not continuous band for the BCCH frequencies
Options
BCCH TCH BCCH + TCH BCCH TCH Dedicated band Common band Dedicated mixed band 45 Nokia Siemens Networks RF hopping workshop / 19.01.2009. BCCH Planning Recommendations Common band strategy 1-2 dB superior UL performance on BCCH TRX better DL performance with small traffic load DL performance on BCCH TRX decreases rapidly with high traffic loads the common band strategy is better when the uplink is considered.
Dedicated band strategy worse performance in UL direction better performance in DL direction when high traffic load (DL performance 1-5 dB better on TCH TRXs) easier to operate because of the stable and easily predictable behavior on the BCCH frequencies in the downlink direction, the dedicated bands strategy is preferable.
Dedicated mixed band strategy separated but not continuous band for the BCCH frequencies, for example, every 4 th
frequency is allocated for BCCH adjacent channel interference is avoided between BCCH frequencies TCH band causes adjacent channel interference for the BCCH frequencies and vice versa
46 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Frequency planning Introduction Since frequency and interference diversity gains significantly depend on the number of hopping frequencies, it is important to ensure that each cell has enough hopping frequencies. RF hopping with fractional load makes it possible to still provide sufficient number of hopping frequencies to the cells even with small TRX configurations.
Decreased fractional load reduces the average channel utilization in the network, thus reducing the probability that interference will occur, making it possible to significantly decrease the frequency reuse distance. 47 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Frequency planning Max frequency load and traffic volume The maximum frequency load on the hopping frequencies is determined by the effective frequency reuse and frequency allocation scheme For example, for the frequency allocation scheme 1/3 (FAR->3) and effective reuse ~6 the maximum peak hour frequency load can be about 30 % (simulated + trialed) It is also important to ensure that the effective reuse is not too low to ensure a good quality. The following table contains an example of choosing the right FAR scheme to give the best capacity gain. As can be seen, the best capacity is got with the FAR 2-5. The minimum effective reuse and maximum frequency load values are still under further consideration. They might be too optimistic for some environments! # of frequencies FAR MA list length Max frequency load Traffic in Erlang # of TCHs Fractional load Effective reuse 1 21,0 8% 13,44 21 13% 8,00 2 10,5 20% 16,80 25 30% 6,72 3 7,0 30% 16,80 25 45% 6,72 4 5,3 40% 16,80 25 60% 6,72 5 4,2 50% 16,80 25 74% 6,72 6 3,5 55% 15,40 23 82% 7,30 7 3,0 60% 14,40 22 92% 7,64 8 2,6 65% 13,65 21 100% 8,00 9 2,3 70% 13,07 20 107% 8,40 21 48 Nokia Siemens Networks RF hopping workshop / 19.01.2009. 3 2 1 1 1 2 2 3 3 3 1 1 1 1 1 1 1 1 1 1 3 2 1 1 4 4 3 1 3 2 4 1 3 2 4 4 2 2 2 1 3 1 3 1 1 1 1 1 1 1 1 1 1 3 5 1 3 2 7 1 3 4 2 7 6 5 1 2 3 4 7 7 FAR Worsening C/I at the cell border Increasing collision probability Max. frequency load 8% 30% 40?% 70?% Frequency planning Frequency Allocation Reuse vs. Frequency Load 49 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Frequency planning Length of MA List A good approach is first to determine the number of frequencies to hop over in each cell. To maximize the frequency and interference diversity gains, it is recommended to use at least four frequencies in MA-lists (this is likely to require fractional load, especially if the TRX configurations in the cells are small) It is also important to ensure that the effective reuse is not too low to ensure a good quality.
Cell_traffic_(Erl) * #_of_TRXs #_of_TRXs*8 * #_of_freqs = Lfreq Cell_traffic_(Erl) 8 * Lfreq = #_of_freqs 50 Nokia Siemens Networks RF hopping workshop / 19.01.2009. 3 2 1 1 1 2 2 3 3 3 1 1 1 1 1 1 1 1 1 1 3 2 1 1 4 4 3 1 3 2 4 1 3 2 4 4 2 2 2 1 3 1 3 1 1 1 1 1 1 1 1 1 1 3 5 1 3 2 7 1 3 4 2 7 6 5 1 2 3 4 7 7 FAR Max. frequency load 8% 30% 40?% 70?% Min. effective reuse 8 7 6.5? 7.5? Frequency planning Frequency Allocation Reuse vs. Frequency Load 51 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Frequency planning Initial frequency load in calculations In practice, the network layout and the surrounding environment have a significant effect on the highest possible frequency load. Highly irregular network layout makes it very difficult to find a good frequency allocation that minimizes interference in all parts of the network. In that case, it might be necessary to restrict the maximum frequency load in order to keep interference acceptable. The recommended approach is to start with a low frequency load and then increase it gradually until the quality threshold is reached.
It is beneficial to avoid big differences in the frequency loads caused by each cell. If the frequency load across the network is kept relatively constant then the interference will be distributed more evenly in the network
52 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Check from the reuse table if 1 FAR scheme is possible Calculate the effective reuse Do you prefer the maximum capacity over good quality Yes Yes No Frequency allocation reuse 1 (=single MA list scheme) Eff reuse 6,5 .. 7 Frequency allocation reuse 3 ~ 5 or frequency sharing No Check from the reuse table the possible FAR schemes Effective reuse > 8 Freq. alloc reuse 3 .. 7 Easy planning preferred over high capacity Calculate the MA list length in a cell basis based on the busy hour traffic estimate and chosen FAR scheme Calculate the average MA list length per area based on the average busy hour traffic per area and 8% average frequency load Eff. reuse and frequency load as a function of frequency allocation reuse 0 2 4 6 8 10 1 2 3 4 5 6 7 8 9 Frequency allocation reuse E f f e c t i v e
r e u s e 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% F r e q u e n c y
l o a d Ef f . reuse Freq. load Reuses and MA list Lengths RF hopping 53 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Planning cases Single MA List Planning Case (1/1 FAR reuse) RF FH with Fractional Load (FAR 3-5) RF FH with Frequency Sharing 54 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Average TRXs/cell : 3. 3 Site Cell TRX count A 1 2 2 3 B 1 4 C 1 4 2 4 3 3 D 1 3 2 4 3 2 E 1 3 2 4 F 1 4 2 3 3 4 G 1 4 2 3 Hoppi ng TRXs 1 2 3 3 3 2 2 3 1 2 3 3 2 3 3 2 Average frequency load 7.4 % (max. 9.9 %) OK 21 frequencies reserved for non-BCCH TRXs Effective reuse = 21 frequencies / 2.4 hopping TRXs per cell = 8.8 OK Network layout: Average hopping TRXs/cell : 2.4 A B C D E F G 1 2 1 1 1 1 1 1 2 2 2 2 2 3 3 3 Average frequency load: 7.4% Single MA List Planning Case (1/1 FAR reuse) Planning case The benefit in single MA-list implementation is that no frequency planning is required, because each cell have the same MA-list containing all the allocated frequencies 55 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Single MA List Planning Case (1/1 FAR reuse) MAIO Planning Since all the cells of a sectorised site are usually controlled by the same BCF, they are frame synchronized. This means that the TDMA frame number is always the same in the sectors of one site. Since the hopping sequence is derived from the HSN and the TDMA frame number, the synchronization makes it possible avoid interference between the sectors of one site.
To prevent intra cell and intra site interference the following requirements have to be fulfilled: All the sectors of one site have to be controlled by the same BCF All the sectors of one site have to use the same HSN MAIO planning have to be properly made
In order to guarantee interference diversity, a different HSN should be used in the different sites located in the same area. 56 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Single MA List Planning Case (1/1 FAR reuse) MAIO Planning It should be checked whether the proper channel separations are possible with allocated frequency band. Channel separation for sectors The minimum requirement for channel separation between sectors is 1. However, in order to avoid constant adjacent channel interference between the sectors of the same site, a separation of 2 is highly recommended. Channel separation for TRXs In order to avoid intra cell interference, the channel separation between the TRXs of the same cell should be at least 2. Preferably the separation should be 3 or more. The goal is to have a minimum channel separation of 2 between the sectors and 3 between the TRXs of the same cell
Parameters used for separation MAIOoffset is used to control the channel separations between the sectors of the same site. MAIOstep defines the channel separation between the TRXs of the same cell. It is thus used to guarantee that intra cell interference doesnt occur. 57 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Single MA List Planning Case (1/1 FAR reuse) MAIO Planning To check if the available frequency band (21 channels in the example) is enough, the following equation is used.
The site to be investigated is the site with biggest TRX configurations that is in this case site C having 3 sectors and 8 hopping TRXs.
As a result, it can be seen that the frequency band of 21 carriers is just enough to allow the implementation of wanted channel separations even in the site with the biggest TRX configurations. The MAIO plan is now made for the Site C by using MAIOstep 3 and by selecting the MAIOoffset parameters for the sectors so that the channel (=MAIO) separation of 2 is realized between the sectors.
If more TRXs are later added, it should me made sure that the MAIO plan for that site is still valid. ( ) min / / / / N N N MAIOstep N S freqs site TRX site cell site cell site = + 21 2 3 3 ) 3 8 ( = + 58 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Site C The sectors share the same HSN MAIO Offset determines the MAIO of the first hopping TRX in each sector MAIOs for the rest of the hopping TRXs are determined by adding MAIO Step to the MAIO of the previous hopping TRX MAI value for each TDMA frame is calculated by BTS and MS by using HSN and TDMA frame number No co- or adjacent channel interference between sectors Transmitted frequencies for each TRX during each TDMA frame Single MA List Planning Case (1/1 FAR reuse) MAIO Planning Example 59 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Site D Site F Site G 60 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Average TRXs/cell : 3. 3 Site Cell TRX count A 1 2 2 3 B 1 4 C 1 4 2 4 3 3 D 1 3 2 4 3 2 E 1 3 2 4 F 1 4 2 3 3 4 G 1 4 2 3 Hoppi ng TRXs 1 2 3 3 3 2 2 3 1 2 3 3 2 3 3 2 19 frequencies reserved for non-BCCH TRXs Network layout: Average frequency load 30.7 % (max. 34.6 %) OK Effective reuse = 19 frequencies / 2.4 hopping TRXs per cell = 7.9 OK Frequency allocation reuse = 19 frequencies / 4.9 FH freqs per cell = 3.9 OK Average hopping TRXs/cell : 2.4 A B C D E F G 1 2 1 1 1 1 1 1 2 2 2 2 2 3 3 3 Average MA list length: 4.9 Average frequency load: 30.7% RF FH with Fractional Load (FAR 3-5) Planning Case The goal is to achieve the highest capacity by employing very tight frequency reuse. 61 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Consecutive carriers allowed in the MA lists MAIO step is set to 2 Fractional load in every sector is 50% or less (fractional load = MAL_length / Nb_TRX) No intra cell adjacent channel interference! Allowing Consecutive Frequencies in MA Lists when MAIOstep = 2 RF FH with Fractional Load (FAR 3-5) MAIO Planning Example 62 Nokia Siemens Networks RF hopping workshop / 19.01.2009. A B C D E F G 1 2 1 1 1 1 1 1 2 2 2 2 2 3 3 3 Average TRXs/cell : 3. 3 Site Cell TRX count A 1 2 2 3 B 1 4 C 1 4 2 4 3 3 D 1 3 2 4 3 2 E 1 3 2 4 F 1 4 2 3 3 4 G 1 4 2 3 Hoppi ng TRXs 1 2 3 3 3 2 2 3 1 2 3 3 2 3 3 2 19 frequencies reserved for non-BCCH TRXs Network layout: Effective reuse = 19 frequencies / 2.4 hopping TRXs per cell = 7.9 OK Average hopping TRXs/cell : 2.4 The same MA list is shared among all the sectors of one site MAIO planning needed Each cell has a sufficient number of hopping frequencies even without fractional loading Frequency allocation reuse = 19 frequencies / 5.4 FH freq.per cell = 3.5 OK Average MA list length: 5.4 RF FH with Frequency Sharing Planning Case 63 Nokia Siemens Networks RF hopping workshop / 19.01.2009. MAIO Step is 1 The sectors share the same HSN MAIO offset for each sector is set so that the MAIOs for TRXs are in consecutive order Frequencies for the MA list are planned with help of frequency planning tool. Minimum separation is 2. Site F as an example. RF FH with Frequency Sharing MAIO Planning Example 64 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Parameters Hopping Power control Handover 65 Nokia Siemens Networks RF hopping workshop / 19.01.2009. FH Parameters Object Parameter Description MA Frequency MA-list. Used with RF FH BTS, max. 63 frequencies per list. BCCH frequency must not be included in the list. MA Identification of MA-list MA-list identification number in a BSC (1 - 128). MA Type of MA-list Frequency band of the MA-list (GSM900, GSM1800, GSM1900). BTS BTS is hopping (HOP) The hopping mode of the BTS (BB, RF or N). BTS Hopping sequence number 1 (HSN1) Hopping sequence number of the hopping group 1. In BB FH for the 0 time slots except the BCCH time slot and in RF FH all the time slots of hopping TRXs (0 - 63). BTS Hopping sequence number 2 (HSN2) Hopping sequence number of the hopping group 2. For the time slots 1-7. BB FH only (0 - 63). BTS MAIO offset Defines the MAIO for the first TRX in the cell (0 - 62). Allows the sharing of the same MA-list between multiple sectors of one BTS without intrasite collisions. Sectors must be under the same BCF. Relevant in RF FH only. BTS MAIO step Defines the step size that is used when the MAIO is calculated for the TRXs in the cell. Relevant in RF FH only. BTS Identification of MA-list MA-list id number identifying the MA-list that is allocated to that BTS. Relevant in RF FH only. TRX Frequency (FREQ) Assign a frequency to a TRX (GSM900 1 - 124, 975 - 1023; GSM1800 512 - 885; GSM1900 313 - 810) 66 Nokia Siemens Networks RF hopping workshop / 19.01.2009. FH Parameters To define a BB-hopping cell the following parameters have to be set: BTS hopping mode (HOP) = BB Hopping sequence number 1 (HSN1) = 0..63 (0 for cyclic hopping and 1..63 for random sequences) Hopping sequence number 2 (HSN2) = 0..63 (0 for cyclic hopping and 1..63 for random sequences) (in most cases HSN1 may equal HSN2) Fixed frequencies for each TRX (FREQ)
To define a RF-hopping cell the following parameters have to be set: BTS hopping mode (HOP) = RF MA-list, MA-list ID and MA-list type must be defined in BSC (max. 63 frequencies) Hopping sequence number 1 (HSN1) = 0..63 (0 for cyclic hopping and 1..63 for random sequences) MAIO offset = 0..62 MAIO step = 0..62 MA-list ID used by the BTS = 0..128
67 Nokia Siemens Networks RF hopping workshop / 19.01.2009. PC Parameters GROUP EXPLANATION Q3 NAME RANGE UNIT Setting General Enable BTS power control powerCtrlEnabled Yes / No Yes Min time interval between PC's powerControlInterval 0 ... 31 sec 1 Power increase step size powerIncrStepsize 2,4 or 6 dB 2 Power decrease step size powerRedStepsize 2 or 4 dB 2 BS tx max pwr preattenuation rfMaxPowerReduction 0 ... 12 dB 0 optional ave UL signal quality (BER)< 0.2 % pwrDecrLimitBand0 0 ... 38 dB 38 ave UL signal quality (BER) 0.2 % - 0.4 % pwrDecrLimitBand1 0 ... 38 dB 20 ave UL signal quality (BER) > 0.4 % pwrDecrLimitBand2 0 ... 38 dB 8 pwrDecrQualFactor 0 / 1 1 optional MS Power optimisation after HO msPwrOptLev -110 ... -47/ N dBm -79 BTS power range Max attenuation bsTxPwrMin 0 ... 30 dB 30 Min attenuation bsTxPwrMax 0 ... 30 dB 0 Averaging windows pcAveragingLevDL 1 ... 32 SACCH 1 weighting 1 ... 3 1 pcAveragingLevUL 1 ... 32 SACCH 1 weighting 1 ... 3 1 pcAveragingQualDL 1 ... 32 SACCH 1 weighting 1 ... 3 1 pcAveragingQualUL 1 ... 32 SACCH 1 weighting 1 ... 3 1
Power control has been found to improve the quality in FH networks and thus, it is recommended to be used in both UL and DL directions. In order to make the PC as fast as possible, the measurement averaging in BTS should be disabled and aggressive power control parameters should be used. 68 Nokia Siemens Networks RF hopping workshop / 19.01.2009. PC Parameters
Power control is the most effective when the used TX power level is kept as low as possible while still maintaining an acceptable link quality. To achieve this, a fast and mainly RXQUAL driven power control is recommended. GROUP EXPLANATION Q3 NAME RANGE UNIT Setting Thresholds pcLowerThresholdsLevDL -110 ... -47 dBm -101 px 1 ... 32 1 nx 1 ... 32 1 pcLowerThresholdsLevUL -110 ... -47 dBm -101 px 1 ... 32 1 nx 1 ... 32 1 pcLowerThresholdsQualDL 0 ... 7 4 px 1 ... 32 1 nx 1 ... 32 1 pcLowerThresholdsQualUL 0 ... 7 4 px 1 ... 32 1 nx 1 ... 32 1 pcUpperThresholdsLevDL -110 ... -47 dBm -47 px 1 ... 32 1 nx 1 ... 32 1 pcUpperThresholdsLevUL -110 ... -47 dBm -47 px 1 ... 32 1 nx 1 ... 32 1 pcUpperThresholdsQualDL 0 ... 7 1 px 1 ... 32 1 nx 1 ... 32 1 pcUpperThresholdsQualUL 0 ... 7 1 px 1 ... 32 1 nx 1 ... 32 1 69 Nokia Siemens Networks RF hopping workshop / 19.01.2009. HO Parameters GROUP EXPLANATION Q3 NAME RANGE UNIT Setting Averaging adjacent Averaging window size for adj cells averagingWindowSizeAdjCell 1 ... 32 SACCH 8 cells Number of zero results allowed numberOfZeroResults 0 ... 7 7 Adj cells averaging: 6 best or 32 allAdjacentCellsAveraged Yes / No No Averaging Method enaFastAveCallSetup Yes / No No enaFastAveHo Yes / No No enaFastAvePC Yes / No Yes Minimum Intervals minIntBetweenUnsuccHoAttempt 0 ... 30 sec 3 minIntBetweenHoReq 0 ... 30 sec 5 Periodic Handovers hoPeriodPBGT 0 ... 63 SACCH 6 HoPeriodUmbrella 0 ... 63 SACCH 6 HO types allowed enableIntraHoInterfUL Yes / No Yes enableIntraHoInterfDL Yes / No Yes enablePwrBudgetHandover Yes / No Yes enableUmbrellaHandover Yes / No No enableMSDistanceProcess Yes / No No enableSDCCHHandover Yes / No Yes Margins Enable HO margin for Lev and Qual enableHoMarginLevQual Yes / No Yes
70 Nokia Siemens Networks RF hopping workshop / 19.01.2009. HO Parameters
Since FH and an aggressive power control cause significant changes in the RXQUAL distribution, the RXQUAL thresholds triggering handovers have to be adjusted accordingly. Normally, the RXQUAL thresholds have to be increased by 1 or 2 classes (RXQUAL 4 -> RXQUAL 5). Also the HO speed should be fast enough but still slower than the PC speed, to ensure that the PC will become triggered before HO Thresholds hoThresholdsLevDL -110 ... -47 dBm -95 px 1 ... 32 1 nx 1 ... 32 1 hoThresholdsLevUL -110 ... -47 dBm -95 px 1 ... 32 1 nx 1 ... 32 1 hoThresholdsQualDL 0 ... 7 5 px 1 ... 32 3 nx 1 ... 32 4 hoThresholdsQualUL 0 ... 7 5 px 1 ... 32 3 nx 1 ... 32 4 hoThresholdsInterferenceDL -110 ... -47 dBm -85 px 1 ... 32 1 nx 1 ... 32 1 hoThresholdsInterferenceUL -110 ... -47 dBm -85 px 1 ... 32 1 nx 1 ... 32 1 msDistanceHoThresholdParam 0 ... 63 TA 63 px 1 ... 32 1 nx 1 ... 32 1
71 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Measurements 72 Nokia Siemens Networks RF hopping workshop / 19.01.2009. KPIs The KPIs to analyze the performance and the quality of the network are basically the same than in the non-hopping network. Only the RXQUAL and Drop Call Rate measures differ from the non- hopping case. Worse RXQUAL can be tolerated when FH is used. Drop call rate doesnt neither correlate directly to the quality, since with FH the drop call rate tends to stay low even though the subjective speech quality were not anymore acceptable. With FH, the criteria for the cumulative uplink and downlink quality distribution could be the following: BSS related indicators Short term criteria Long term criteria Uplink quality distribution 05, 95% 05, 98% Downlink quality distribution 05, 95% 05, 98%
73 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Difference in RXQUAL Distribution nonFH <-> FH When frequency allocation reuse gets tighter and tighter -> less samples in quality class 0, more quality samples in classes 1-5 With PC the same effect can be seen The more traffic load, the stronger the change in distribution Bigger change in DL RXQUAL distribution
Worse RXQUAL doesnt necessarily mean worse subjective speech quality!! 74 Nokia Siemens Networks RF hopping workshop / 19.01.2009. DL RXQUAL Distribution 0,00 10,00 20,00 30,00 40,00 50,00 60,00 70,00 80,00 90,00 100,00 q 0 q 1 q 2 q 3 q 4 q 5 q 6 q 7 Quality Classes P e r c e n t a g e
( % ) No FH 1/3 pure 1/3 heuristic 1/1 DL/UL RXQual Distribution UL RXQUAL Distribution 0,00 10,00 20,00 30,00 40,00 50,00 60,00 70,00 80,00 90,00 100,00 q 0 q 1 q 2 q 3 q 4 q 5 q 6 q 7 Quality Classes P e r c e n t a g e
( % ) No FH 1/3 pure 1/3 heuristic 1/1 75 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Subjective quality, laboratory tests Steady quality/FER value (fast mobile or frequency hopping) RXqual FER 0 - 4 good 0 - 4% good 5 slightly degraded 4 - 15% slightly degraded 6 degraded 15 - 35% degraded 7 useless >35% useless RXQUAL and FER Subjective speech quality The FER is a measure of how successfully the speech frame was received after the error correction process and it is thus a better indication of the subjective speech quality compared to the RXQUAL which gives an estimate of the link quality in terms of BER.
FER corresponds better to the subjective speech quality FER doesnt match directly to RXQuality FER / MOS values can be measured in DL direction with measurement system UL FER available in OSS statistics. DL FER uses Enhanced Measurement Reports It may be concluded that in the frequency hopping networks significant quality deterioration starts at RXQUAL class 6 while in non-hopping network this happens at RXQUAL class 5.
76 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Feature interworking 77 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Feature interworking Half rate The interleaving depth of the TCH/HR is four instead of eight as it is in TCH/FR. Because the interleaving has a significant effect on the successful error correction of the speech frame, especially on the frequency hopping networks utilizing low frequency allocation reuse and fractional loading, the performance of frequency hopping may be reduced. The use of cyclic hopping with even number of hopping frequencies should be avoided in networks utilizing half rate. Since the half rate channel is transmitted on every second TDMA frame, the usage of cyclic hopping with even number of frequencies means that one half rate connection uses only half of the frequencies. This problem doesnt occur if random hopping sequences are used. Extended cell range Baseband hopping cannot be used. Radio frequency (RF) hopping cannot be used in E-TRXs. (E)GPRS (E)GPRS supports both Baseband and Synthesized Frequency Hopping 78 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Feature interworking Common BCCH Frequency Hopping between the bands of operation is not supported. The segment architecture enables having BTSs without a BCCH TRX. This reduces the number of hopping groups in a BTS's regular area, because there is no need for a separate group for the BCCH TRX in RF hopping. DOCUMENTTYPE TypeUnitOrDepartmentHere TypeYourNameHere TypeDateHere BB hopping PGSM900 BTS, EGSM900 BTS, GSM1800 BTS, Three Hopping groups two hopping group two hopping group RF hopping PGSM900 BTS, EGSM900 BTS, GSM1800 BTS, Two groups one hopping group one hopping group 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 7 6 5 4 3 1 2 0 79 Nokia Siemens Networks RF hopping workshop / 19.01.2009. BTS configurations Hardware support Maximum configuration 80 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Hardware support BB hopping supported only 2nd generation BTS BB and RF hopping support (RTC support BB hopping only) Talk family with AFE MetroSite (pseudo BB hopping) UltraSite FlexiEDGE
Frequency Sharing The basic requirement in frequency sharing (e.g. 1/1 reuse, 3/3 reuse) is that the cells at one site have to be controlled by the same BCF, so that they are frame synchronized. Refer to the next slide. 81 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Maximum BTS configurations supporting Frequency Hopping BTS type Baseband hopping Note RF hopping Note Talk-family Omni 12 TRXs 12 TRXs Sectorised 4+4+4 TRXs 4+4+4 TRXs MetroSite Omni 4 TRXs 1) 4 TRXs Sectorised 2+2 TRXs 1) 2+2 TRXs UltraSite Omni 12 TRXs 12 TRXs Sectorised 2) 2) Flexi EDGE Omni 12 TRXs 12 TRXs Sectorised 3) 3) 1) MetroSite BB hopping is pseudo-BB hopping. The same hopping group of the cell cannot include both normal TRXs and high-power TRXs. 2) UltraSite limitations for sector configuration are: a maximum of 12 TRXs / sector and a maximum of 6 sectors / BCF. Thus the possible sector configurations go from 2+2+2+2+2+2 TRXs to 6+6 TRXs. The same hopping group of the cell cannot include both normal TRXs and highpower TRXs. 3) Flexi EDGE limitations for sector configuration are: a maximum of 12 TRXs / sector, a maximum of 6 sectors / BCF and a maximum 24 TRXs / BCF. The same hopping group of the cell cannot include both normal TRXs and double power TRXs or IDD TRXs when antenna or BB hopping is used. 82 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Activating RF hopping 83 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Activating RF hopping A 4+4 BTS is modified so that the whole site is RF hopping and uses one MA list.
Create the MA list (1) for the GSM band (EBE). The list includes frequencies 10,11,12,13,14,15,16,17,18,19,20 and 21. ZEBE:1,900:FREQ=10&11&12&13&14&15&16&17&18&19&20&21; Lock the BTSs so that the hopping mode and hopping sequence number of the BTSs can be modified (EQS). ZEQS:BTS=1:L; ZEQS:BTS=2:L; Attach the MA list to the BTSs and define the MAIO offset and MAIO step values. Set the hopping modes to RF hopping and define HSN1 (EQA, EQE).If the same frequencies are used, make sure that the hopping channels do not overlap between sectors. Each frequency is used only once during one frame period, provided that the HSN values are equal between the sectors. ZEQA:BTS=1:MAL=1,MO=0,MS=2; The MS parameter will be available for use in the ZEQA command only if FLEX_MAIO_USAGE is activated. Use the command ZWOA:2,466,A:; to activate it. ZEQE:BTS=1:HOP=RF,HSN1=1; ZEQA:BTS=2:MAL=1,MO=6,MS=2; ZEQE:BTS=2:HOP=RF,HSN1=1; Unlock the BTSs (EQS). ZEQS:BTS=1:U; ZEQS:BTS=2:U; 84 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Activating RF hopping Example of a situation before activating Freeform RF Hopping:
BTS=2 HOP=N TRX=5 FREQ=13 TRX=6 FREQ=14 TRX=7 FREQ=15 TRX=8 FREQ=3 CH0=MBCCHC 85 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Activating RF hopping This is the example situation after the Freeform RF hopping activation procedure has been completed:
BTS=1 HOP=RF MAL=1 MO=0 MS=2 HSN1=1 TRX=1 FREQ=1 CH0=MBCCHC BCCH TRX does not hop. TRX=2 MAIO=0 ! TRXs 2-7 hop over TRX=3 MAIO=2 ! frequencies in MAL=1 TRX=4 MAIO=4 ! without collisions. ! The system allocates MAIOs BTS=2 HOP=RF MAL=1 MO=6 MS=2 HSN1=1 ! for the RTSLs. TRX=5 MAIO=6 ! TRX=6 MAIO=8 ! TRX=7 MAIO=10 ! TRX=8 FREQ=3 CH0=MBCCHC BCCH TRX does not hop.
86 Nokia Siemens Networks RF hopping workshop / 19.01.2009. Conclusions RF FH offers a more flexible way to increase the capacity than BB FH and works with narrow bandwidths and variable capacity requirements 1/1 reuse with MAIO management dont offer the maximum capacity gain but offer an easy planning Frequency allocation reuse 3-5 with intelligent planning tool offers the maximum capacity gain and easy plan transfer to the network
Best capacity and quality is achieved with the right site selection and right antenna installation + height Cell specific (heuristic) frequency planning and frequency list planning (FH) is required with every solution when the best quality is required Theoretical frequency reuse factors will not provide good quality in a challenging environment when the network layout planning is compromised 87 Nokia Siemens Networks RF hopping workshop / 19.01.2009. FH considerations Frequency and interference diversity gains? Gain vs. reuse BB or RF FH? Cyclic or random sequence? Channel separation? Frequency allocation strategy? Minimum Effective Reuses? The Best Frequency Allocation reuse Maximum frequency load? PC / HO gain with FH? PC / HO parameters? Support of planning and optimization tools? BER or subjective speech quality?