Professional Documents
Culture Documents
Introduction to
Radio Fine Tuning
BSS release B8
1.1
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
1.2
1.3
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
1.4
1.5
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Theoretical presentation
Coverage problem
Interference problem
Unbalanced power budget problem
TCH Congestion problem
Deducing the right team for intervention
Exercises
1.6
1.7
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Theoretical presentation
Coverage problem
Interference problem
Unbalanced power budget problem
TCH Congestion problem
Deducing the right team for intervention
Exercises
Symptoms:
Customers complain about dropped calls or/and no network
OMC QoS indicators
TCH failure rate
Call drop rate
Low proportion of better cell HO
High rate of DL quality HO
A interface indicators
High rate of Clear Request messages, cause radio interface failure
1.8
No information is available on non-covered parts of the network, as there are non-mobiles making calls over there!
Nevertheless, cells in border of non-covered zones do have a particular behavior:
B
A
Cell A will mainly perform Better Cell handovers towards its neighbors, whereas cell B, bordering the non-coverage
area, will perform emergency handovers for MSs exiting the network.
For these MS, mainly DL Quality HO will be triggered:
DL because MS antenna is less efficient than BTS one,
Quality rather than Level since Qual has a greater priority in Alcatel HO causes.
1.10
Frequency RxLev_UL RxLev_DL RxQual_UL RxQual_DL Path_loss_UL Path_loss_DL delta_Path_loss delta_quality AV_MS_PW R nb_of samples
119 -89.29 -84.67 0.42 0.43 123.82 123.67 0.15 -0.01 34.53 3074
92 -89.77 -89.09 0.41 0.38 124.87 128.09 -3.21 0.03 35.11 10253
111 -83.15 -79.15 0.17 0.33 116.05 121.22 -5.16 -0.16 32.9 5339
1.11
It could have been coverage problems if this trace was made for 3 mono-TRX cells. In this case, the 3 lines are
uncorrelated. Anyway, delta path loss of frequency 111 is greater than 5dB, showing a problem on this TRX.
If this is a 3-TRX cell, it cannot be a coverage problem as the three TRXs are not impacted. It will be either interference
or malfunction of one TRE.
If the trace is done on 3 mono-TRX cells, in that case, it could be a coverage problem. Be careful when interpreting this
result table: even if average levels in the UL and the DL are high and a lot of Quality problems are seen, nobody can
say that samples with bad quality have a good level ! The level seen is just an average
One should have a look to the next slide
RxLev -95
BC_UL: 358 3 .4 9 %
I n t_ D L : 0 %
BC_D L: 244 2 .3 8 % < R x L e v _ S e r v i n g > = - 1 0 6 .1 7 d B m
N e ig h _ C e ll_ N b B S IC < L ev> S a m p le s RxQual > 4
0 2 - 1 0 4 .6 4 67
1 5 - 1 0 7 .5 0 48 Interference
F r e q u e n c y :1 1 1
N u m b e r_ U L :5 3 3 9
N u m b e r_ D L :5 3 3 9
RxLev > -95
In t_ U L : 0 0 .0 0 %
BC_UL: 290 5 .4 3 %
RxQual > 4
I n t_ D L : 0 %
BC_D L: 626 1 1 .7 3 % < R x L e v _ S e r v i n g > = - 1 0 6 .5 6 d B m
N e ig h _ C e ll_ N b B S IC < L ev> S a m p le s
10 2 - 1 0 1 .5 4 63
1.12
All samples are Bad Coverage samples (BC). None is interference, showing that this cell is not facing any interference
problem.
Not acceptable
coverage limit:
Too low level
Too bad quality
1.13
A coverage problem is observed when a significant amount of the traffic of a cell is suffering from both low level and bad
quality (RxQual).
To confirm, distribution of samples per RXLEV band should be also considered to know the proportion of calls which are
experiencing a low signal level.
If a lot of samples of low level and bad quality are observed for only a sub-part of the TRXs (can be one only) then a
BTS hardware problem or a problem on the antennae should be suspected.
If all the TRXs are experiencing a lot of samples of low level and bad quality then a coverage problem must be
suspected.
These RMS indicators are provided on RNO tool per TRX, per Cell:
Matrix of Number of Measurement Results per DL RxQual value and per DL RxLev band
RMQLDSAM = RMS_DL_RxQuality_RxLevel_sample
Vector of Percentage of Samples per DL RxLev band
RMQLDLVDV = RMS_DL_RxLevel_distrib
Vector of Percentage of Samples per DL RxQual band
RMQLDQUDV = RMS_DL_RxQuality_distrib
Not acceptable
coverage limit: Acceptable coverage limit:
Too low level Sufficient level and good quality
Too bad quality
1.14
In order to know if the coverage problem is due to a big amount of traffic at the cell border or rather to indoor calls, the
average TA value per RXQUAL value and RXLEV band as well as the Percentage of TA values over TA threshold
should be observed.
Matrix of Average TA per UL RxQual value and per UL RxLev band
RMQLUTAM = RMS_UL_RxQuality_RxLevel_TimingAdvance
Rate of Measurements Results whose TA is greater than the TA threshold
RMTAGTR = RMS_TimingAdvance_greater_threshold_rate
Maximum TA value of all values reported in Measurement Results
RMTAMXN = RMS_TimingAdvance_max
1.15
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Theoretical presentation
Coverage problem
Interference problem
Unbalanced power budget problem
TCH Congestion problem
Deducing the right team for intervention
Exercises
Definition: Interference
A network facing interference problems presents good RxLev and
bad RxQual in the same time on some areas.
Symptoms
Customers complain about bad speech quality (noisy calls) and/or
call drops
OMC QoS indicators
SDCCH/TCH Drop
Low proportion of better cell HO
High rate of DL/UL quality HO and interference HO
Low HO success rate
A interface indicators
High rate of Clear Request messages, cause radio interface
failure
1.16
Mainly, interferences are in the DL, due to bad frequency planning introducing interferences in the network. And this
problem will not change till the frequency plan is not returned
Sometimes, interference can be in the UL in very dense area (for example, microcell area), since MSs are very close.
Finally, sometimes interferences are not coming from BS or MS but from another radio equipment, either in the UL or
the DL.
1.17
The feature Radio Measurement Statistics (RMS) is designed to make far easier the work for planning and optimization
of the network by providing the operator with useful statistics on reported radio measurements.
In fact these statistics give directly the real cell characteristics by taking into account the MS distribution.
Thanks to this feature, the operator is able to:
detect interfered frequencies.
assess the quality of the cell coverage.
detect and quantify cell unexpected propagation.
assess the traffic distribution in the cell from statistics on reported neighboring cells.
evaluate the voice quality in the cell.
etc.
In regards to the RTCH Measurements Observation (measurement type 11), the Radio Measurement Statistics
(RMS) bring the following advantages:
smaller report files.
the report files always have the same maximum length whatever the measurement duration is.
every measurement is taken into account (no sampling).
no more need for measurement post-processing tools for statistics. Directly available with RNO or NPA.
It is directly linked to
Voice Quality
These RMS indicators are provided on RNO tool per TRX, per Cell:
Matrix of Number of Measurements Results per CFE band (or BFI band) and per UL RxLev band
RMFEM = RMS_UL_ConsecutiveFrameErasure_RxLevel_sample
Vector of Average number of Consecutive Frame Erasure per UL RxLev band
RMFEBFAV = RMS_UL_ConsecutiveFrameErasure_avg_per_RxLevel
Vector of Average UL RxQual per RxLev band
RMQLUQUAV = RMS_UL_RxQuality_avg_per_RxLevel
GSM interference
co-channel
adjacent
1.20
Level
F(BTS1) F(BTS2)
6 dB
F(BTS1)=F(BTS2)+1 Frequency
1.21
GSM Interference
Co-Channel interference
-12 dB are sufficient (-9 dB according GSM)
Level
-12 dB
F(BTS1)=F(BTS2) Frequency
1.23
Examination
Neighbor cells in Abis trace (only for BCCH)
Non-neighbor cells in RMS (MAFA frequencies)
Frequency planning C/I < 12 dB
Correction
Downtilt increase of interferer, or even change of antenna
orientation
Reduction of BS power, Change of frequency
Concentric cell implementation (1 extra TRX needed if traffic
cannot be supported by Outer+Inner configuration)
1.24
MS1 indoor 2
1.25
When interferences are created by frequency plannig, its not so hard to detect them. But frequency planning tools
mainly consider DL C/I and coverage.
Some problems are more difficult to predict. For example, lets consider a microcell layer:
B
A
A and B are 2 microcells with the coverage described before in dense urban environment.
Even if both cells A & B are using adjacent frequencies (5 and 6), the overlapping area is far from cell A
antenna. Thus, in this area C/I is lower than 6 dB.
A red MS is connected on cell A. When the MS starts its call, it transmits full power and a PC algorithm quickly
reduces MS power as the received level is very good (microcell coverage). When MS A enters the building, it
faces a loss of signal of 20 dB. Then, MS power increases to MS_TXPWR_MAX.
A second mobile B is connected to cell B and moves down in the coverage area of cell B. MS power of B
decreases quickly down to MS_TXPWR_MIN as the MS is close to the antenna. But when MS B arrives outside
the building where A is sitting, A and B are close and transmitting on adjacent frequencies Then B has to
increase its power to avoid dropping its call. By the way, global level of freq B is increased in all cell B
creating interference in the UL.
1.26
umbrella
capture FDR
microcell
The situation described on the slide corresponds to the usage of FDR in a single layer network. This is in that case a
heavy-to-tune algorithm presenting of lot of interference and bad quality call risks, since the mobile will be connected to
a cell when being not in its service area.
1.27
Other RF interferers:
medical devices: GSM equipments disturb them more than the opposite !
anti-theft mechanisms.
Example:
Microcell
antenna
shop
The Microcell is showing a very high call drop rate. On one frequency, very small call duration.
No problem seen in the frequency plannig. No potential interferer.
Abis trace:
Qual DL Qual
UL
Level Level
interference
The Spectrum analyzer connected on the antenna feeder highlights a peak on GSM freq 6 in the UL
Anti-theft mechanism turned off: no more problem
1.28
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Theoretical presentation
Coverage problem
Interference problem
Unbalanced power budget problem
TCH Congestion problem
Deducing the right team for intervention
Exercises
UL Quality HO is triggered:
UL since the problem is in the UL.
Quality as Quality has greater priority than level.
Examination:
RMS
Path Balance vector per TRX
Number of calls with abnormal bad FER (good
RxQual & bad FER)
Abis monitoring:
|delta path-loss| > 5dB)
check if problem is occurring for 1 TRX or all
1.30
Problem on 1 TRX: FU/CU or TRE problem or ANY problem or cables connected to this equipment.
All TRXs: problem on antenna, feeder, jumper or common equipment (ex: ANX, ANC).
delta_Path_loss
nb_of samples
AV_MS_PWR
Path_loss_UL
Path_loss_DL
delta_quality
RxQual_UL
RxQual_DL
Frequency
RxLev_UL
RxLev_DL
106 -9 4 . 5 2 -8 7 . 1 9 0.43 0.25 127.55 130.19 -2 . 6 4 0.18 33.03 2066
89 -8 4 . 2 9 -7 5 . 1 7 0.65 0.44 115.32 118.17 -2 . 8 5 0.21 31.03 2001
118 -9 0 . 7 5 -8 3 . 3 6 0.46 0.41 123.22 126.36 -3 . 1 4 0.04 32.46 3193
124 -8 8 . 8 9 -8 5 . 3 0 0.29 0.67 120.48 128.30 -7 . 8 2 -0 . 3 7 31.59 2931
D IS TR IB U TIO N O F U P L IN K Q U A L ITY
F re q u e n c y Q u a l0 Q u a l1 Q u a l2 Q u a l3 Q u a l4 Q u a l5 Q u a l6 Q u a l7 B a d _ Q u a lit y
106 84.75 % 4.07 % 3.68 % 3.19 % 1.36 % 1.50 % 0.92 % 0.53 % 2.95 %
89 81.41 % 1.70 % 2.95 % 3.65 % 6.35 % 2.55 % 1.30 % 0.10 % 3.95 %
118 83.62 % 4.23 % 4.23 % 3.35 % 1.57 % 1.79 % 0.97 % 0.25 % 3.01 %
124 90.79 % 1.06 % 2.18 % 2.35 % 1.77 % 1.30 % 0.48 % 0.07 % 1.84 %
D IS TR IB U TIO N O F D O W N L IN K Q U A L ITY
F re q u e n c y Q u a l0 Q u a l1 Q u a l2 Q u a l3 Q u a l4 Q u a l5 Q u a l6 Q u a l7 B a d _ Q u a lit y
106 90.27 % 3.44 % 2.08 % 1.55 % 0.92 % 1.36 % 0.34 % 0.05 % 1.74 %
89 80.16 % 6.45 % 7.00 % 3.85 % 1.50 % 0.50 % 0.45 % 0.10 % 1.05 %
118 86.78 % 2.72 % 3.95 % 1.82 % 1.41 % 1.13 % 1.19 % 1.00 % 3.32 %
124 77.14 % 4.37 % 5.87 % 5.94 % 3.48 % 1.36 % 0.82 % 1.02 % 3.21 %
1.31
Fair average Path Balance at Cell level can hide a bad value
for one TRX
1.32
These RMS indicators are provided on RNO tool per TRX, per Cell:
Vector of the Number of Measurement Results per Path Balance band
RMPBV = RMS_PathBalance_sample
Average Path Balance value
RMPBAN = RMS_PathBalance_avg
1.33
Every BTS has its proper architecture and the diagnosis must be adapted.
1.34
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Theoretical presentation
Coverage problem
Interference problem
Unbalanced power budget problem
TCH Congestion problem
Deducing the right team for intervention
Exercises
1.35
1.36
Cells on wheel operational by several operators around the world for special events coverage & capacity
IRMA (SFR) connected to Caens BSC.
Orange coverage / Football WC 1998 for Paris Stade de France :
Specific cells covering Paris Stadium. During games, only small capacity (using joker frequencies).
During breaks, some TRX off cells around are turned off, and frequencies are reused for stadium cells.
Add TRXs to reach the new target configuration and find joker
frequencies and / or implement concentric cells.
1.37
Warning: offered traffic is not the capacity delivered by the system but the traffic asked by the users.
1.38
Half rate may not only mean SW solution. Need of G2 BSC/TC, Evolium TRE or G2 DRFU.
1.39
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Theoretical presentation
Coverage problem
Interference problem
Unbalanced power budget problem
TCH Congestion problem
Deducing the right team for intervention
Exercises
Correction
Check the tuning of default radio parameters
action
Planning team
Standard parameters ?
Maintenance team
Dimensionning team
Consult the config. db No Yes Choose an (other) classical algo
1.40
Coverage problem:
If the field reality does not match the RNP prediction
Maintenance team to change physical configuration (tilt,
azimuth, antenna height, etc.) and drive test team to
check it
1.41
Interference problem:
Planning team to identify the interference source and correct
it (joker frequency, new frequency planning, etc.)
1.42
1.43
1.44
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
1.45
1.46
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Theoretical presentation
Radio measurements principles
Radio measurements data processing
Radio Link Supervision and Power control
Handover Detection
Handover Candidate Cell Evaluation
Handover Management
Exercise
JUSTIFICATION
When the detected problem does not concern another team (Network planning and
frequency planning, Dimensioning, Radio engineering, Maintenance) or
when the other teams cannot give any solution (too tight frequency planning, no
additional TRX available, no financial budget for new sites, etc.)
the Radio Fine Tuning team has to find a compromise between:
High traffic density (Erl/km/Hz)
High quality of service (Call drop, CSSR, Speech quality, indoor, etc.)
1.47
1.48
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Theoretical presentation
Radio measurements principles
Radio measurements data processing
Radio Link Supervision and Power control
Handover Detection
Handover Candidate Cell Evaluation
Handover Management
Exercise
1.49
The BTS sends a SYS_INFO_5 message that contains the list of neighbor cells for connected mode. (The
SYS_INFO_2 message contains the list of neighbor cells for idle mode).
Sys info 2bis, 2ter, 5bis and 5ter are also used for multiband networks.
MS reporting depends on EN_INTERBAND_NEIGH and on MULTIBAND_REPORTING parameters.
The MS may report:
6 strongest cells of any band (MULTIBAND_REPORTING=0), or
5 strongest cells of the serving band + 1 strongest cell of another band
(MULTIBAND_REPORTING=1), or
4+2 (MULTIBAND_REPORTING=2), or
3+3 (MULTIBAND_REPORTING=3).
RXLEV
Range: [-110dBm, -47dBm]
Binary range: [0, 63]; 0=-110dBm, 63=-47dBm
The higher the physical or binary value, the higher the receiving level
RXQUAL
Range: [0.14%, 18.10%]
Binary range: [0, 7]; 0=0.14%, 7=18.10%
The lower the physical or binary value, the lower the bit error rate, the better the quality
0-2=excellent; 3=good; 4=ok; 5=bad; 6=very bad; 7=not acceptable
Candidate cell
HO execution
evaluation
The BSC is computing algorithms
usually using average value (sliding window) of these measurements
1.50
The BTS starts sending MEASUREMENT RESULT messages as soon as it receives the RL ESTABLISH INDICATION
message from the MS.
The BTS stops sending MEASUREMENT RESULT messages upon receipt of one of the two following messages:
DEACTIVATE SACCH
RF CHANNEL RELEASE
L1 Info
L3 Info
Measurement
Report
From the MS
1.51
SACCH BFI: bad frame indicator; 2 values 0 or 1; 0 means that the BTS succeeded in decoding the measurement
report.
--------TCH--------->
TCH establishment.
.
Extended Measurement
ASSIGNT COMPLETE ------------------------------------------------------- >
ASSIGNMENT COMPLETE ----------------------------------- >
Results include the average
<------SACCH--------
--------SACCH------>
ASSIGNMENT COMPLETE
signal level measured on
<------SACCH--------
--------SACCH------>
each MAFA frequency over
<-------SACCH--------
EMO one SACCH mf duration
(MAFA freq. List)
.
.
EMR received once per call
.
--------SACCH------>
on SACCH
EMR
(MAFA freq. RxLev)
1.52
When the BTS receives a CHANNEL ACTIVATION with the Extended Measurement Order (EMO) included, it must
send this information on the SACCH to the corresponding mobile only once.
When the BTS has to send this information, it must replace the sending of system information 5, 5bis, 5ter or 6 by this
information. At the next SACCH multiframe, the BTS must resume the sending of this system information by the
replaced one.
The EMO must be sent after 2 complete sets of SYS_INFO5 and 6, i.e. after the 2nd SYSINFO 6 after the reception of
SABM. This guarantees the MS has received a complete set.
Then, the BTS normally receives from the MS an EXTENDED MEASUREMENT RESULT with the level of the
frequencies to monitor. The BTS must make the correlation between these levels and the frequencies contained in the
latest EMO information, after having decoded them, according to the order of the ARFCN. The
EXTENDED_MEASUREMENT_RESULT is NOT forwarded to the BSC, instead a MEASUREMENT_RESULT with
indication no_MS_results is sent to the BSC.
In particular, the BTS must identify the level of the BCCH frequency of the serving cell (which must always be part of
the frequencies to monitor) and apply it as the RXLEV_DL in the Radio Measurement Statistics. The other frequencies
will be considered in the same way as the BCCH frequency of neighbor cells: they will be linked to the neighbor level
and C/I statistics.
Time allowed:
5 minutes
1.53
Explain why cell 2 has a very high outgoing HO unsuccessful rate and a high
call drop
Cell 3 CI=6169
GSM900
(7, 62)
CI=6169
GSM900
Cell 2 CI=1964
GSM900
(3,46) Cell 1
(7, 62)
1.54
1.55
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Theoretical presentation
Radio measurements principles
Radio measurements data processing
Radio Link Supervision and Power control
Handover Detection
Handover Candidate Cell Evaluation
Handover Management
Exercise
BTS BSC
Radio Active
Link Channel
Measurements Pre-processing
the
Assignment of radio measurements data processing functions in th e ALCATEL BSS
1.56
The active channel pre-processing function calculates average values of signal levels, qualities and timing advance
provided by the radio link measurements function.
The pre-processing is based on a sliding window averaging technique. The averaging is either weighted or unweighted
depending on the type of the input parameters.
1.58
The pre-processing function is stopped when a HANDOVER COMMAND is emitted by the serving BSC. At this time,
the MEASUREMENT RESULT messages are ignored by the pre-processing function and no update of the book-
keeping tables or averaging is done anymore.
The pre-processing function is enabled again (in case of failure of an intracell or intercell handover) after reception of
either messages listed above, and the old measurements are kept in the book-keeping list and taken into account in
the new averaging.
The pre-processing function is completely handled by the BSC. The input parameters of this function are provided by
the BTS every SACCH multiframe in the MEASUREMENT RESULT message.
The function calculates average values of levels, qualities and timing advance. The pre-processing method is based on
a sliding window averaging technique. The pre-processing is done for every measurement sample, i.e. every SACCH
multiframe. The averaging intervals are expressed in terms of SACCH multiframe periods and their range is between 1
and 31.
The averaging process for any variable can start as soon as A_YYYY_XX (YYYY stands for LEV, QUAL, PBGT or
RANGE and XX for HO, DR, PC or MCHO) samples, each with MEAS_VALID bit set to 0 (validity indicator
reported by the MS in the MEASUREMENT REPORT message), are actually available except in case of the averaging
of the received level from the neighbor cells and the averaging of AV_RXLEV_PBGT_HO, AV_BS_TXPWR_HO and
AV_BS_TXPWR_DR.
105,00
100,00
95,00
90,00
85,00
80,00 level
75,00 average (w indow 4)
1 2 3 4 average (w indow 8)
5 6 7 8 9
1.59
The calculation of levels, qualities and timing advance (i.e. distance information) uses a variety of averaging window
sizes as well as specific weighting factors for quality estimates.
One separate window exists for:
power control on the uplink and the downlink (A_LEV_PC , A_QUAL_PC),
emergency handover (A_LEV_HO , A_QUAL_HO , A_RANGE_HO),
fast emergency handover for microcells (A_LEV_MCHO),
better cell handover and better zone handover (A_PBGT_HO) for intra-layer, interlayer and interzone
handovers,
forced directed retry (A_PBGT_DR),
neighbor filtering and ranking for all HOs (A_PBGT_HO),
codec adaptation (A_QUAL_CA_HR_FR , A_QUAL_CA_FR_HR).
Experiences
some experiments have shown that the number of HOs is very
sensitive to modification of these values
1.60
At BSC level,
Input flows
MEASUREMENT RESULT
Control flows
active channel pre-processing configuration parameters for PC:
A_LEV_PC, W_LEV_PC, A_QUAL_PC and W_QUAL_PC,
active channel pre-processing configuration parameters for HO:
A_LEV_HO, W_LEV_HO, A_PBGT_HO, W_PBGT_HO, A_QUAL_HO, W_QUAL_HO,
A_RANGE_HO, A_LEV_MCHO, W_LEV_MCHO, A_PBGT_DR.
cells list for book-keeping:
BA_IND_SACCH: indicator of the change of the BA_allocation,
NBR_ADJ: number of declared adjacent cells of the serving cell denoted by n,
for n=1 to NBR_ADJ: BSIC(n) and FREQ(n).
Output flows
Averaged measurements for power control:
AV_RXQUAL_UL_PC ; AV_RXLEV_UL_PC: MS power control/threshold comparison,
AV_RXQUAL_DL_PC ; AV_RXLEV_DL_PC: BS power control/threshold comparison.
Averaged measurements for handover detection:
AV_RXQUAL_UL_HO, AV_RXQUAL_DL_HO, AV_RXLEV_UL_MCHO,
AV_RXLEV_UL_HO, AV_RXLEV_DL_HO, AV_RXLEV_DL_MCHO,
AV_LOAD , averaged traffic load
AV_BS_TXPWR_HO, AV_RANGE_HO,
AV_RXLEV_PBGT_HO, AV_RXLEV_NCELL(n), AV_RXLEV_NCELL_BIS(n).
AV_RXLEV_PBGT_DR,
AV_RXLEV_NCELL_DR(n), n=1..BTSnum.
BFI_SACCH
AV_RXQUAL_xx_CA_HR_FR, AV_RXQUAL_xx_CA_FR_HR
MS_TXPOWER_CONF / BS_POWER: last power level reported by the MS and transmit power currently
used by the BS.
1.61
An MS is required to measure the BCCH power level of a number of BCCH frequencies. These measurements are
used for the power budget computation in the BSC and the candidate cell evaluation in the BSC.
The MS reports to the BTS, in the MEASUREMENT REPORT message, the measurements of the NO_NCELL_M
(NO_NCELL_M <= 6) best cells it receives (RXLEV_NCELL, BCCH frequency index and BSIC number) for each
multiframe. In case of multiband capability, the mobile reports the best cells of each supported frequency band (if
available). This reporting is allowed at BSS level by the flag EN_INTERBAND_NEIGH and it is specified by the
parameter MULTIBAND_REPORTING.
The adjacent cells reported by an MS can change over the averaging interval. The book-keeping function keeps a table
composed of the last 32 reported adjacent cells, the maximum number of which is NBR_ADJ. The total number of
adjacent cells for which measurements reported by the MSs are available within the average interval is BTSnum.
The BSC G1 maintains a table of up to 150 cells, from which up to 64 can be declared as adjacent cells to a given cell.
The BSC G2 maintains a list of up to 1000 cells, from which up to 64 can be declared as adjacent cells to a given cell.
Because the maximum number of adjacent cells may be greater than 32, the number of adjacent BCCH frequencies is
limited to 32. Moreover, a mechanism for overwriting obsolete entries in the bookkeeping table, when new cells are
reported, is provided.
When the variable BTSnum reaches its maximum value of 32 and at least one new cell has to be entered in the list,
then the BSC sorts out all cells in the bookkeeping list, which have been reported with signal level = 0 for the last 20
measurements (10 seconds).
This is done by summing the raw measurement values over the last 20 samples. All the corresponding cell entries are
cleared from the bookkeeping list, BTSnum is decreased by the number of cleared entries and some of the vacant
entries are used to include the new cells.
Time allowed:
10 minutes
1.62
Fill up the table with average function. The chart will be automatically processed
The fact that there may not be enough cleared entries to store new measurements is excluded, see justification below:
Because the MS must resynchronize at most every 10s with the neighbor cells it monitors, it is useless to keep cells in
the bookkeeping list which have not been reported for more than 10s, it will be impossible to makkes an handover
towards these cells.
Therefore, the overwriting mechanism described above will function correctly if there are less than 32 cells reported in
every 10s, which makes an average rate of 3 new cells per second.
The potentiality of overflow of the book-keeping list is therefore excluded.
The book-keeping is performed according to the BSIC and BCCH frequency couple. This function updates the table
every multiframe except if the measurement report is missing or Measurement Valid Bit is set to not valid. When the
level of a cell is not reported, a zero must be entered as measurement value. For each multiframe and for each of the
NO_NCELL_M cell measurements it receives, the function has to check the BSIC number and the BCCH frequency
index (FREQ(n)).
When the couple (BSIC, BCCH frequency) is not in the reference list (received from the OMC), the corresponding
measurements should be discarded.
The BTSnum variable is updated every multiframe except if the measurement report from the MS is missing. It is
incremented by the number of new couples (BSIC number, BCCH frequency index) registered as described above.
Remark: Two cells can have the same BSIC number or the same BCCH frequency index. Therefore, the couple of
these parameters is needed to define a cell.
1.63
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Theoretical presentation
Radio measurements principles
Radio measurements data processing
Radio Link Supervision and Power control
Handover Detection
Handover Candidate Cell Evaluation
Handover Management
Exercise
BTS BSC
Radio Radio
Link Link
Supervision Command
Radio Active
Link Channel
Measurements Pre-processing PC Threshold
PC Command
Comparison
1.64
The two main functions specified in this document and implemented in the ALCATEL BSS are:
Radio link supervision and radio link command:
These functions handle the detection of the radio link failure so that calls which fail either from loss of
radio coverage or unacceptable interference are satisfactorily handled by the network. The radio link
supervision is responsible for detection of the loss of the radio link, based on incorrectly received
SACCH frames. The radio link command is responsible for commanding to set the power at a maximum
level for radio link recovery or to clear the call when the radio link has failed.
The radio link recovery can be activated or not, depending on a configuration flag (EN_RL_RECOV).
The radio link failure procedure is always running and clears the call when the radio link has failed.
Power control:
This function handles the adaptive control of the RF transmit power from the MS and the BS. The RF
power control aims at minimizing the co-channel interference and also at reducing the DC power
consumption of the MS. This function is in charge of detecting a need for a power command and then of
applying this power command. Therefore it can be divided into two processes: PC threshold comparison
and PC command. MS and BS power control are operating independently, they can be activated or not,
depending on configuration flags (EN_MS_PC and EN_BS_PC).
All these functions require directly or indirectly input parameters provided by the function in charge of the radio link
measurements.
Most of the input data required by the power control functions are provided by Active channel pre-processing function.
Principles
1.65
The determination of the radio link failure is based on a counter. According to the GSM Technical Specification 05.08
for the BSS, the criterion for incrementing/decrementing this counter should be based:
either on the error rate on the uplink SACCH,
or on RXLEV/RXQUAL measurements of the MS.
In the ALCATEL BSS, it is based on the number of SACCH frames which cannot be decoded.
It must be stressed that this criterion is related to the first one recommended above but it is not exactly the same. The
ALCATEL criterion is in fact the one recommended by the GSM Technical Specification 05.08 for the MS.
RLTO_BS
18
(T100)
RLTO
of uplink radio link 16
SACCH block lost: - 1
Initial value of S = BS_RADIO_LINK_TIMEOUT
N_BS_TXPWR_M
13
if S reaches N_BSTXPWR_M, a radio link
Radio link Recovery
recovery is triggered (optional)
if S reaches 0, a radio link failure is detected SACCH block received: + 2
RADIOLINK_TIMEOUT_BS S S
0 0
RADIOLINK_TIMEOUT is important because Radio link Failure
The radio link supervision function is performed in the BTS and it uses three parameters given to the BTS in the TRX
configuration data message:
EN_RL_RECOV: flag enabling/disabling the sending of CONNECTION FAILURE INDICATION by the BTS
when the need for radio link recovery is detected,
N_BSTXPWR_M: threshold for the radio link recovery,
RADIOLINK_TIMEOUT_BS: threshold (number of SACCH messages) for the radio link failure.
In addition, the function handles a counter named S. RADIOLINK_TIMEOUT_BS is the initial and maximum value of S.
For each SACCH not decoded, S is decremented by 1 while for each SACCH decoded, it is incremented by 2.
The incrementation or decrementation is performed if the following condition is met:
RADIOLINK_TIMEOUT_BS >= counter S >= 0.
As soon as the counter S is equal to the threshold N_BSTXPWR_M, the radio link recovery is triggered if
EN_RL_RECOV = ENABLE. Therefore, in the case where the shadowing is so strong that all SACCH frames
are lost, the radio link recovery will be triggered after (RADIOLINK_TIMEOUT_BS - N_BSTXPWR_M) SACCH
periods.
S = f [ BFI(t) ]
25
RAD IO_LIN K_TIM EOU T_B S
N_BSTXPW R_M
15
S value
BFI
S
10
0
1 3 5 7 9 11 13 15 17 19 21 23 25 27 29
SA C C H n u m b er
1.67
Received events
Activate supervision: activation of the radio link supervision from the BTS telecom layer 3,
SACCH, BFI = 1: not decoded SACCH frame,
SACCH, BFI = 0: decoded SACCH frame,
Note: the BFI flag is internal to the BTS and does not deal with the BFI flag defined by the GSM.
Deactivate supervision: deactivation of the radio link supervision by the BTS telecom layer 3.
Transmitted events
Radio link recovery: indication sent to the radio link command function in order to set the BS and MS powers to
the maximum.
Radio link failure: indication sent to the radio link command function in order to release the call.
These events are sent to the BSC in the CONNECTION FAILURE INDICATION message:
In case of Radio link recovery, the BTS sends only once (to avoid overload of the Abis interface) the
CONNECTION FAILURE INDICATION message to the BSC with cause "set MS/BS-TXPWR-M (value: '001
1111', reserved for National use). This action (message formatting) is performed by the GSM layer 3.
In case of Radio link failure, the BTS sends the CONNECTION FAILURE INDICATION message with cause
'Radio link Failure' to the BSC.
Thus, the CONNECTION FAILURE INDICATION message on Abis is not showing any call drop. One should look at
the cause of CONFAIL.
1.68
The action consists in increasing the power of the MS and of the BTS to their maximum, in a single step, if the link is
failing, i.e. the BTS is not able to decode the SACCH anymore for some period of time.
This functionality is performed upon reception of the CONNECTION FAILURE INDICATION message (cause set
MS/BS-TXPWR-M) from the BTS. This message can be sent by the BTS only if EN_RL_RECOV = ENABLE. Upon
reception of this message, the radio link command function:
1. sends to the BTS a power increase command up to BS_TXPWR_MAX (BS_TXPWR_MAX_INNER if the MS is
on the inner zone of a concentric or multiband cell) in the BS POWER CONTROL message.
2. sends to the MS a power increase command up to min(MS_TXPWR_MAX,P) (min
(MS_TXPWR_MAX_INNER,P) if the MS is in the inner zone of a concentric or multiband cell) in the message
MS POWER CONTROL.
When a radio link recovery occurs, the radio link command function gives an indication to the power control function
once the power increase has been commanded.
The maximum power increase of the MS is 2dB per 60 ms. Thus, if MS_TXPWR_MAX=33dBm and
MS_TXPWR_MIN=13dBm, the MS coming from MIN to Max will take 600 ms.
Note: the BS Power Control process does not interfere with the recovery procedure since the former comes to a halt when
no SACCH multiframe is received. Thus, the BS power control process does not take into account the radio link
recovery event.
The task of the radio link command consists in informing the call control function to release the call.
Concentric cell or multiband cell
The power value BS_TXPWR_MAX_INNER is applied in case of radio link recovery for an MS in the inner zone. The
power value BS_TXPWR_MAX is applied in case of radio link recovery for an MS on an outer zone channel.
Note: the radio link supervision procedure will function also if SACCH frames are not lost continuously, but with a
longer reaction time.
Time allowed:
5 minutes 1.70
d ow
nlin
Minimum power levels: RXLEV_UL
up
lin k
k
RXLEV_DL
1.71
The main objective of the power control, in connection with handover algorithms, is to allow a maximum number of MSs
to operate in the network while maintaining a minimum interference level.
The algorithms must ensure that any mobile is connected with the cell in which the output powers from the MS and the
BS are as low as possible (to reduce MS power consumption and interference in the network) while keeping a
satisfactory link quality.
When on a sufficient duration, the propagation conditions keep worsening, then action must be taken.
The first action is to increase the output power levels at the MS or the BS. When the maximum allowed value has been
reached, a handover may become necessary.
To reflect this philosophy in macrocells (not in microcellular environment), the algorithm allows for handover on quality
and strength reasons only when the last step of power control has been reached. If propagation conditions worsen
rapidly when the MS is at low power, the power control algorithm allows to reach quickly the maximum power.
Nevertheless great care must be taken in choosing the relative values of the thresholds for power control and handover
as well as the averaging window sizes (smaller window size and higher threshold for power control than for handover).
It must be remembered that, although it is desired that the MS transmits with the lowest possible power, it is more
important not to lose a call. Thus early triggering for the power control is possible, by choosing, small values for the
averaging window sizes and higher comparison thresholds.
Does not decrease power if the resulting level is below the low
level threshold
1.72
The threshold comparison process detects the need to change the MS power level. This detection is done by
comparison between the averaged values produced by the active channel pre-processing function and thresholds.
U_RXQUAL_UL_P
1
L_RXQUAL_UL_P
2
1.73
A need for a PC command is detected when one of the conditions above is true. Then, the information for the execution
of the PC command is given to the PC command process.
The MS power control function can be disabled with a flag EN_MS_PC. This flag is changeable from the OMC-R.
Note: The GSM coding of quality is contra-intuitive, since the value 0 codes for the best quality and 7 for the worst. Thus,
the comparison between two quality values must be understood in the opposite way in terms of quality.
Note: POW_RED_STEP_SIZE is used in two ways: for PC_COMMAND (decrease of MS power) and for
PC_THRESHOD_COMPARISON (to avoid ping-pong effect).
Power increase: If
AV_RXQUAL_UL_PC > L_RXQUAL_UL_P + OFFSET_RXQUAL_FH
AV_RXQUAL_UL_PC L_RXQUAL_UL_P + OFFSET_RXQUAL_FH
and AV_RXLEV_UL_PC < L_RXLEV_UL_P
Then PC_COMMAND(MS, INC, MS_P_INC dB, <min(MS_TXPWR_MAX, P))
Power decrease: If
AV_RXQUAL_UL_PC < U_RXQUAL_UL_P
and AV_RXLEV_UL_PC >= L_RXLEV_UL_P + POW_RED_STEP_SIZE
1.74
1.75
Whenever any of the threshold conditions occurs, a PC command must be sent to the MS over the air interface.
In order to compute the adaptive power step size, the middle threshold between the upper threshold U_RXLEV_UL_P
and the lower threshold L_RXLEV_UL_P is considered.
This threshold is regarded as the target received level around which the MS should always stay. The following
algorithm tries to maintain and bring the MS power closer to this target threshold. The size of the power step is limited
to MAX_POW_INC for an increase of the MS power and MAX_POW_RED for a decrease of the MS power.
When the received level is between the two thresholds U_RXLEV_UL_P and L_RXLEV_UL_P (i.e. no need to change
the level) and a power control on quality cause is triggered, fixed power step sizes are applied: POW_INC_STEP_SIZE
for power increase and POW_RED_STEP_SIZE for power decrease.
Two weighting factors POW_INC_FACTOR (for power increase) and POW_RED_FACTOR (for power decrease) allow
to modify the reactivity of the algorithm (the more POW_INC_FACTOR is nearby 1, the greater the reactivity of the
algorithm is and the larger the power step size is).
The target received level is TARGET_RXLEV_UL for the uplink path.
TARGET_RXLEV_UL corresponds to the next higher multiple of 1 dB from (U_RXLEV_UL_P + L_RXLEV_UL_P)/2.
Example
4 SACCH=1 Measurement 3. MR
p/dBm Report (MR) Need for PC command
2. MR 4. MR
detected
-80
PC Command
-90 20dB
Fast Power Control
POW_INC_STEP_SIZE=6dB
-100 Normal Power Control
-110
t/ms
0 480 960 1440 1920
t/ms
60 180 300 420
1.76
1.77
In the equations:
MS_TXPWR is the last MS_TXPWR_CONF value reported by the BTS.
roundup means round to its next higher multiple of 2 dB.
rounddown means round to its next lower multiple of 2 dB.
The rate of change of MS power is required to be one nominal 2 dB step every 60 msec. Thus a 30 dB step change
should be accomplished in 900 msec. The operator should be warned of this as it may impact on the choice of settings
for MS_P_CON_ACK and MS_P_CON_INT.
Then the ordered value of the MS transmit power, called MS_TXPWR, is sent to the MS as follows:
The BSC sends the MS POWER CONTROL message to the BTS (i.e. to the TRX handling the relevant
channel) which then forwards the PC command to the MS in the Layer 1 header.
The MS applies the PC command and confirms this action by transmitting the applied power value
(MS_TXPWR_CONF) on the uplink SACCH in the layer 1 header.
On SACCH channel, the MS may not send the MEASUREMENT REPORT message (e.g. in case of transmission of
Short Message).
In this case, the BSC receives a MEASUREMENT RESULT message which does not contain the
MEASUREMENT REPORT. The BSC takes into account the MS_TXPWR_CONF variable.
1.78
OFFSET_RXQUAL_FH
Algorithm:
If Frequency hopping applied
then OFFSET_RXQUAL_FH = Offset_hopping_PC
Else OFFSET_RXQUAL_FH = 0
1.79
In order to take into account the frequency hopping in the RXQUAL evaluation, the variable OFFSET_RXQUAL_FH is
introduced.
If on the corresponding channel, Frequency hopping is applied then OFFSET_RXQUAL_FH = Offset_Hopping_PC
otherwise OFFSET_RXQUAL_FH = 0
Offset_Hopping_PC is a parameter defined on a per cell basis.
PC Downlink in Frequency hopping case
In this case, the BSC inhibits the BS power control on all the channels which use the BCCH carrier. The entity
performing the BS power control in the BSC gets all the information concerning a new channel and decides
whether to activate the BS power control for this channel. The power control must be inhibited when the
frequency used by the new channel is the same as the frequency used for the BCCH in the BTS (cell) in which
the channel is activated.
For any channel which has the BCCH frequency in its hopping sequence (MA), the MS is measuring a very
good downlink level each time it hops on the BCCH. To avoid that this results in a too optimistic average, it is
possible to require from the MS not to include the BCCH measurement in the averages. This is achieved by
setting the PWRC flag to 1 in the SYSTEM INFORMATION type 6 message sent by the BSS on the SACCH.
If the channel is hopping only on the BCCH frequency (after a transmitter failure), it is considered as a non-
hopping channel and it is concerned by the non-frequency hopping case.
Timers
T_SDCCH_PC allows the inhibition of PC on SDCCH
1.80
The timer T_SDCCH_PC allows to inhibit the MS and BS power control on SDCCH.
This timer is changeable at the OMC-R level on a per cell basis. It is triggered upon receipt of the ESTABLISH
INDICATION message after SDCCH activation for immediate assignment procedure. As long as the timer runs,
the power control is inhibited on SDCCH.
If the timer expires, the power control will be enabled again on SDCCH.
If the timer is running at the sending of the RF CHANNEL RELEASE message, the timer is stopped.
T_SDCCH_PC is useful in case of long SDCCH phases.
During SDCCH for call establishment, PC disabled should be preferred with a view to secure call setup. Nevertheless,
if SMS usage is very high, SDCCH phases may be long. In this case, to avoid interference, PC will be enabled after
T_SDCCH_PC expiry (about 5s).
After any PC command is sent to the MS, some time must be expected before MS_TXPWR_CONF (power
confirmation sent by the MS on the uplink SACCH) can reach the desired value. The timer MS_P_CON_ACK is
triggered after any power modification command to monitor that the desired transmission power MS_TXPWR is
reached.
If MS_P_CON_ACK elapses before the expected value of MS_TXPWR_CONF is received, the power control
decision process is resumed immediately with the last MS_TXPWR_CONF received.
If the expected value of MS_TXPWR_CONF is received before the timer MS_P_CON_ACK is elapsed, the
timer MS_P_CON_ACK is stopped and the timer MS_P_CON_INT is triggered. Then the MS PC threshold
comparison process is resumed with MS_TXPWR_CONF for the same MS as soon as MS_P_CON_INT
expires.
1.81
1.82
According to GSM Technical Specification 05.08 section 7.1, the BCCH carrier must be broadcast with a constant
power in the cell. In this release of the ALCATEL BSS, this constant value is set to the maximum power allowed in the
cell that is defined by the parameter BS_TXPWR_MAX.
This means that all dedicated channels (TCH, SDCCH) which are on the BCCH frequency must always be
transmitted with the maximum power, i.e. the BCCH power must not be changed by the BS power control
function.
Power control UL
(Remark: Use the default parameters document)
What happens if we do not use Frequency Hopping?
Why is it better to have A_LEV_PC=A_LEV_HO/2?
Thresholds:
Lower QUAL of RX uplink = 3
High QUAL of RX uplink = 2
Lower LEV of RX uplink = -90dBm
Upper LEV of RX uplink = -75dBm
POW_RED_STEP_SIZE= 4
POW_INC_STEP_SIZE= 6
Put the right threshold in the next slide chart
Time allowed:
25 minutes 1.83
Power control UL
Qual QUESTION
For each case
PC triggered?
Step size value?
With
POW_INC_FACTOR=0,6
And
POW_RED_FACTOR=0,6
and
MAX_POW_INC=MAX_PO
W_RED=8
Lev
Nb of case ---> 1 2 3 4 5 6
AV_RXQUAL_UL_PC 0 1 2 6 3 4
AV_RXLEV_UL_PC -98 -80 -73 -69 -86 -91
Power control
Delta value
1.84
Power control DL
Thresholds:
L_RXLEV_DL_P = -85dBm POW_INC_FACTOR = 0.6
U_RXLEV_DL_P = -75dBm POW_RED_FACTOR = 0.8
L_RXQUAL_DL_P = 2.9 MAX_POW_INC = 16dB
U_RXQUAL_DL_P = 1 MAX_POW_RED = 16dB
A_QUAL_PC = 4 BS_P_CON_ACK = 3s
A_LEV_PC = 4 BS_TXPWR_MIN = -16dB
Using the Trace Abis Excel file, find each parameter value:
POW_INC_STEP_SIZE = ? BS_P_CON_INT = ?
POW_RED_STEP_SIZE = ? OFFSET_RXQUAL_FH = 0 or 1 ?
1.85
1.86
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Theoretical presentation
Radio measurements principles
Radio measurements data processing
Radio Link Supervision and Power control
Handover Detection
Handover Candidate Cell Evaluation
Handover Management
Exercise
1.87
1.88
BTS BSC
HO Preparation
Radio Active
Link HO Candidate
Channel HO Detection
Measurements Cell Evaluation
Pre-processing
HO
management
HO
protocol
MSC
1.89
The HO Preparation function can also be named "handover algorithms" as the algorithms described are the "heart" of
this function.
The ALCATEL handover preparation is derived from the basic algorithm found in Annex A of the GSM
Technical Specification 05.08.
The handover preparation is in charge of detecting a need for handover and proposing a list of target cells.
Therefore it can be divided into two processes: handover detection and handover candidate cell evaluation.
The handover detection process analyzes the radio measurements reported by the BTS and triggers the candidate cell
evaluation process each time a handover cause (emergency or better cell type) is fulfilled.
The handover candidate cell evaluation works out a list of possible candidate cells for the handover. This list is sorted
according to the evaluation of each cell as well as the layer they belong to (in a hierarchical network) and the frequency
band they use (in a multiband network).
Once the handover preparation is completed, the handover decision and execution (handover management entity) is
performed under the MSC or BSC control. The directed retry preparation is performed by the handover preparation
function.
Once the directed retry preparation is completed, the directed retry is performed either under the BSC control
(internal directed retry) or under the MSC control (external directed retry).
An example of implementation of these functions except for directed retry is given in the GSM Technical Specification
05.08.
The handover preparation requires indirectly input parameters provided by the function in charge of the radio link
measurements.
Most of the input data required by the handover functions are provided by a function called: Active channel pre-
processing.
The figure above depicts in a general way:
the interconnections between these functions,
the implementation of these functions in the ALCATEL BSS.
1.90
In case of a handover alarm, the handover detection process gives to the cell evaluation process:
the preferred target cell layer: lower, upper or none.
the raw candidate cell list, which can be either all neighbors, or the subset which verify the handover causes
(plus other specific cells in particular cases). With each cell is given one of the handover causes which have
been verified.
The cause of handover.
Four main handover categories are provided, depending on the cause of handover and the context of application. The
context of application for a handover is either "intercell" (the handover is performed between two different cells) or
"intracell" (the handover is performed in the same cell).
The detection of a need for handover is performed through handover causes which are going to be detailed.
The cause of handover is based either on a situation of emergency (this cause is therefore called "emergency cause")
or on the existence of better conditions. In this last case, the name of the cause depends on the context of application:
for intercell handovers, it is called "Better cell cause". For intracell handovers, it is called "Better zone cause", as it is
applied only in the case of interzone handovers in concentric or multiband cells.
OFFSET_RXQUAL_FH
and AV_RXLEV_UL_HO <= RXLEV_UL_IH
and MS_TXPWR = min (P, MS_TXPWR_MAX)
and EN_RXQUAL_UL= ENABLE
1.92
OFFSET_RXQUAL_FH
and AV_RXLEV_UL_HO < L_RXLEV_UL_H
and MS_TXPWR = min (P, MS_TXPWR_MAX)
and EN_RXLEV_UL= ENABLE
1.93
OFFSET_RXQUAL_FH
and AV_RXLEV_DL_HO <= RXLEV_DL_IH
and BS_TXPWR = BS_TXPWR_MAX
and EN_RXQUAL_DL= ENABLE
1.94
OFFSET_RXQUAL_FH
AV_RXLEV_DL_HO < L_RXLEV_DL_H
BS_TXPWR = BS_TXPWR_MAX
and EN_RXLEV_DL= ENABLE
1.95
1.96
This cause is used when a dominant cell provides a lot of scattered coverages inside other cells, due to propagation
conditions of the operational network. The consequence of these spurious coverages is the probable production of a
high level of co-channel interference.
This cause is different from the others as it is more preventive. It does not make use of the propagation conditions of a
call. It just does not allow an MS to talk to a BTS if it is too far away.
It may happen for example that some peculiar propagation conditions exist at one point in time that provide exceptional
quality and level although the serving BTS is far and another is closer and should be the one the mobile should be
connected to if the conditions were normal.
It may then happen that these exceptional conditions suddenly drop and the link is lost, which would not have
happened if the mobile had been connected to the closest cell. So for these reasons, this cause does not wait for the
power control to react.
May be triggered
From inner zone of a concentric cell
Towards outer zone, same cell
OUTER INNER
1.97
CAUSE 10: too low level on the uplink in the inner zone
1.98
CAUSE 11: too low level on the downlink in the inner zone
1.99
May be triggered
From outer zone of a concentric cell
Towards inner zone, same cell
OUTER INNER
1.100
1.101
ZONE_HO_HYST_UL
UL static hysteresis for interzone HO from outer to inner
In case of multi-band cell, should take into account the difference of
propagation between GSM and DCS
Added to cause 10 threshold RXLEV_UL_ZONE
ZONE_HO_HYST_DL
DL static hysteresis for interzone HO from outer to inner
In case of multi-band cell, should take into account the difference of
propagation between GSM and DCS and the difference of BTS
transmission power in the two bands
Added to cause 11 threshold RXLEV_DL_ZONE
1.102
PING_PONG_MARGIN(0,call_ref)
Penalty PING_PONG_HCP put on cause 13 if
The immediately preceding zone in which the call has been is the
inner zone of the serving cell
And The last handover was not external intracell
And T_HCP is still running
PING_PONG_MARGIN(0,call_ref) = 0
If the call was not previously in servings inner zone
Or T_HCP has expired
OUTER INNER
1.103
EN_CAUSE_13
Load balance between inner and outer zones may be allowed
by setting EN_LOAD_BALANCE = ENABLE
If EN_LOAD_BALANCE = ENABLE
If INNER zone is less loaded than OUTER,
EN_CAUSE_13 = ENABLE
If INNER zone is more loaded than OUTER,
EN_CAUSE_13 = DISABLE
If EN_LOAD_BALANCE = DISABLE
EN_CAUSE_13 = ENABLE
1.105
1.106
The only restrictions are linked to EN_MULTI-BAND_PBGT_HO and EN_BI-BAND_MS parameters.
OUTER INNER ?
?
1.107
1.108
1.109
In this case, there is another cell with a better power budget i.e., the link quality can be improved or maintained with a
reduced transmit power of both the MS and the BTS. The radio link is not degraded but there is the opportunity to
decrease the overall interference level by changing the serving cell of the given MS.
In conjunction with power control, it presents the advantage to keep the interference as low as possible, since it
minimizes the path loss between the BTS and the MS.
This cause is especially designed to cope with the requirement that the mobile should be connected with the cell with
which the lowest possible output powers are used. To assess which of the cells is this "best cell", the algorithm
performs every measurement reporting period the comparison of the path loss in the current and in the neighbor cell.
This is a feature special to GSM which is made possible because the mobile measures the adjacent cell signal levels
and reports the six best ones.
This power budget gives the difference in path loss between the current cell and the adjacent cells reported by the
mobile.
When PBGT(n) is greater than 0, then the path loss from cell n is less than the path loss from the serving cell and thus
the radiated power in the downlink direction, and therefore in the uplink direction as well, will be lower in cell n than in
the current cell.
However it would not be advisable to hand over the MS to another cell as soon as PBGT is greater than 0, because the
MS would probably oscillate between the two adjacent cells as the propagation conditions vary. An hysteresis
mechanism is implemented to avoid this undesirable effect.
1.110
The MS may be handed over from the serving cell indexed 0 to a neighbor cell indexed n only if the power budget
exceeds the handover Margin(0,n). The handover Margin(0,n) can be modified according to the traffic situation in the
serving cell and the neighbor cell n. In this way, power budget handover can be delayed towards a loaded cell and
traffic load handover can be triggered from a loaded cell. Once the MS is handed over, the same algorithm is applied in
the new cell, and a new PBGT is computed (which will be close to the opposite value of PBGT in the old cell) and
compared to a new HOMargin. (Thus, the global hysteresis (from cell 0 to cell n and back to cell 0) is the sum of the
two HOMargins).
However, It is still possible that a ping-pong mechanism is created by different handover causes, for instance a
handover may be triggered towards a neighbor cell for bad quality, but in the neighbor cell, a handover back may be
triggered for power budget reasons. In order to avoid this, an additional anti-ping-pong mechanism is implemented in
the power budget calculation. It enables to penalize for a certain time the cell on which the call has been before.
In case of handover from SDCCH to SDCCH, this cause does not take the traffic situation into account.
In multiband cell environment, the mobile can operate in a different band than the frequency band of the BCCHs. This
can lead to circular ping-pong handovers from the inner zone if the new band is DCS 1800 or to the impossibility to
trigger PBGT handovers from the inner zone if the preferred band is GSM 900.
To avoid this problem, when the MS is in the inner zone of a multiband cell, it may be handed over from the serving cell
indexed 0 to a neighbor multiband cell indexed n only if the power budget exceeds the handover Margin(0,n) plus the
offset handover margin which allows to handicap or favor the PBGT (In the inner zone, the cause power budget is
only checked between multiband cells, in a way to maintain the MS in the preferred band).
The offset handover margin can possibly be used in concentric cells.
AV_RXLEV_NCELL
received level of BCCH of neighbor cell
AV_RXLEV_PBGT_HO
received level of serving cell (BCCH or not)
AV_RXLEV_NCELL - AV_RXLEV_PBGT_HO
the highest is the best neighbor cell
but serving might not be at the maximum level (with DL
power control)
necessity to have a corrective factor
1.111
BS_TXPWR_MAX AV_BS_TXPWR_HO
AV_RXLEV_NCELL-[AV_RXLEV_PBGT_HO+(BS_TXPWR_MAX-
AV_BS_TXPWR_HO)]
compare received level of neighbor and serving cells as if the
serving one was emitting at the maximum level
1.112
MS_TXPWR_MAX(n)
maximum emitting power for the MS in neighbor cell n
MS_TXPWR_MAX
maximum emitting power for the MS in the serving cell
MS_TXPWR_MAX(n) - MS_TXPWR_MAX
Corrective factor to compensate for the difference of maximum power of
each cell
MS_TXPWR_MAX(n) - MS_TXPWR_MAX = bts_max_power(n) -
bts_max_power
which should be the case if delta_path_loss is equilibrated
if not exact, can be corrected with HO_MARGIN(0,n)
1.113
Then, another correction factor must be taken into account because the maximum BS powers of the serving and
neighbor cells may be different:
TXPWR= MS_TXPWR_MAX(n) - MS_TXPWR_MAX.
As the first step of calculation is based on the downlink parameters, this correction factor should be based on the
maximum BS powers used in the serving and neighbor cells.
Two reasons (which are not completely de-correlated) for not using the BS powers can be envisaged:
for a given cell, the GSM does not specify formally the maximum BS power of the neighbor cells. Only
BS_TXPWR_MAX is defined (it is sent on the air interface),
it is not easy for the evaluating BSC to know the maximum BS powers of the neighbor cells.
The use of the maximum MS powers requires that the difference of MS powers is equal to the difference of BS powers.
This condition is met in most cases. If it is not the case, the difference can be corrected by the operator with the
HO_MARGIN(0,n) parameter (HO hysteresis).
PBGT >0: the neighbor cell is more advantageous as the path loss is lower than in the current cell.
PBGT <0: the serving cell is more advantageous than the current cell.
1.114
The main drawback of this handover category is the risk of "ping-pong " effect, which is an oscillating back and forth
handover between two (or three) cells. As the "better cell" handovers are meant to find the "best cell", the variation of
the radio conditions will trigger a big amount of better cell handovers, if the algorithms have a too sensitive reaction.
Hence, some mechanisms are forecast, in order to prevent these oscillations from occurring repeatedly at given places.
Case 3:
ping_pong_margin example Not a ping-pong case
OK with ping_pong_margin
Case 2: and T_HCP
ping-pong in normal case
OK with ping_pong_margin
Case 1: OK
1.115
Warning: this mechanism is not applied for emergency handovers (new mechanism in B7 exists for capture HO, based
on T_INHIBIT_CPT timer).
If EN_TRAFFIC_HO(0,n)=ENABLE
Then PBGT(n) > HO_MARGIN(0,n) + OFFSET_HO_MARGIN_INNER
+ max(0, DELTA_HO_MARGIN(0,n))
(n=1BTSnum)
Else PBGT(n) > HO _MARGIN(0,n) + OFFSET_HO_MARGIN_INNER
Cause 12 HO is correlated with HO cause 23. This is why there are two equations according to the activation of HO
cause 23 (EN_TRAFFIC_HO).
Mechanism to avoid PBGT HO if the level from the serving cell is high enough
RXLEV_LIMIT_PBGT_HO: threshold above which it is not necessary to trigger a
handover on power budget
AV_RXLEV_PBGT_HO: average of the received levels over A_PBGT_HO measurements
1.117
W/O B6 WITH B6
1.118
DELTA_HO_MARGIN(0,n) is evaluated according to the traffic situation of the serving cell and the neighbor cell n
(Traffic_load(n)) in the following way:
If Traffic_load(0)=high and Traffic_load(n)=low
DELTA_HO_MARGIN(0,n)= -DELTA_DEC_HO_margin
If Traffic_load(0)=low and Traffic_load(n)=high
DELTA_HO_MARGIN(0,n)= DELTA_INC_HO_margin
else DELTA_HO_MARGIN(0,n)=0
where DELTA_DEC_HO_margin allows the cause 23 (traffic handover) detection.
When the traffic in the serving cell is high and is low in the cell n:
DELTA_INC_HO_margin allows to penalize the cause 12 detection when the traffic in the serving cell is low
and is high in the cell n.
Note:
In the case of concentric or multiband cells, if the channel is in the inner zone (ZONE_TYPE = INNER),
BS_TXPWR_MAX and MS_TXPWR_MAX in equation must be replaced by BS_TXPWR_MAX_INNER and
MS_TXPWR_MAX_INNER respectively.
If the channel is in the outer zone (ZONE_TYPE = OUTER), the formulation of equation is not changed.
Note: The value of PBGT(n) is calculated every SACCH period for each neighbor cell n whose measures are kept in the
book-keeping list.
1.119
TCH_INFO_PERIOD = 5s period used by the BSC to count the number of free TCHs.
1.120
The principle of this handover is to reduce the size of the serving cell when it is high-loaded relatively to a low-loaded
cell.
When the mobile moves away from the BTS, the power budget will increase and a better cell handover will be triggered
earlier.
It is recommended to inhibit Traffic handover towards 1-TRX cells. These cells do not have enough resources to
receive incoming handovers due to congestion of neighbor cells. Moreover because of the great variation of traffic in
the 1-TRX cells, traffic load is never considered as low.
This cause is inhibited for handover from SDCCH to SDCCH.
Cause 23 is checked over all the neighboring cells belonging to the same layer. It means that it is checked between
cells whose CELL_LAYER_TYPE is single or upper, between cells whose CELL_LAYER_TYPE is lower, and between
cells whose CELL_LAYER_TYPE is indoor.
In addition to the condition on the cell layer type, the cell frequency band condition for checking Cause 23 is as follows
whether or not the MS is in the inner zone of a multi-band cell:
a) The MS is not in the inner zone of a multi-band cell
If the flag EN_MULTI-BAND_PBGT_HO is set to disabled, Cause 23 must not be checked between
cells which use different frequency bands (i.e cells having different CELL_BAND_TYPE).
If the flag EN_MULTI-BAND_PBGT_HO is set to enabled, Cause 23 will be checked over all the
neighboring cells without any cell frequency band restriction.
b) The MS is in the inner zone of a multi-band cell
If the flag EN_MULTI-BAND_PBGT_HO is set to disabled, Cause 23 is checked over all the
neighboring cell multi-band cells (FREQUENCY_RANGE= PGSM-DCS1800 or EGSM-DCS1800) which
belong to the same BSC as the serving cell.
If the flag EN_MULTI-BAND_PBGT_HO is set to enabled, Cause 23 will be checked over all the
neighboring cells without any cell frequency band restriction.
+ DELTA_HO_MARGIN(0,n) (n=1BTSnum)
This constraint is less discriminative than Cause 12
In specific traffic distribution, this cause is triggered before cause
12
1.121
1.122
The figure represents the triggering areas of PBGT and traffic handovers according to the traffic load in the serving cell
and in the neighbor cell.
1.123
Directed Retry
1.124
1.125
Pre-ranking
using PREF_LAYER, PRIORITY(0,n), frequency band
Filtering process
AV_RXLEV_NCELL_DR(n) > RXLEVmin(n)
+max(0,MS_TXPWR_MAX(n) - P)
Number of free TCHs t(n) > FREElevel_DR(n)
1.126
1.127
Can be used to capture traffic by any cell, whatever its type, band,
etc.
1.128
Case the serving cell is in the upper or single layer (CELL_LAYER_TYPE(n0) = upper or single):
Condition 1: The immediately preceding cell n-1 is in the indoor or lower layer, i.e. CELL_LAYER_TYPE(n1) =
lower or indoor, or the frequency band of the immediately preceding cell n-1 is different from the frequency band of
the serving cell n0, i.e. CELL_BAND_TYPE(n1) <> CELL_BAND_TYPE(n0).
Condition 2: The call has previously performed i) an emergency internal handover on quality (Cause 2, 4, and 7)
towards the serving cell or ii) an external handover with the A interface GSM cause uplink quality or downlink
quality and there is a bi-directional adjacency link between the preceding external cell n-1and the serving cell n0.
HO
Congested cell
O
H
Most appropriated MS
to be pushed out
1.130
1.131
1.132
HO alarm NO
Cause 28?
Start HO
Cause number (28) Check first 2 OK
conditions of
NO YES Reference of the call to handover Cause 28
END NOK T_FILTER is started
(which corresponds to the first
candidate MS received)
END
1.133
HO cause 28 process:
If EN_FAST_TRAFFIC_HO = enable, when an assignment request (or external emergency HO request) is
queued, the RAM process sends to the HOP process a Fast Traffic HO request which contains the queued
request reference and its channel rate.
Then, HO cause 28 becomes checkable (EN_CAUSE_28=enable).
Once an HO alarm for cause 28 is triggered, the flag EN_CAUSE_28 is set to disable so as not to perform
more than one handover. In the same time, the HOP process gets back to the RAM process a Fast Traffic HO
Acknowledge which contains the queued request reference and the reference of the MS that can perform HO.
If several answers are sent to the RAM process, only the first one corresponding to the queued request is taken
into account.
The RAM process checks if the request is still queued. If that is so, the RAM process asks the HOP
process to start HO for this mobile; otherwise the process is stopped.
Once the HOP process receives this message, the first two conditions of Cause 28 (good enough level, enough
free resources in the target cell) are checked one more time. If the conditions are fulfilled, the HOP process
sends an alarm to the HOM entity and the timer T_FILTER is started ; otherwise the process is stopped.
Note: the first two conditions of cause 28 are tested twice in order to be sure that the candidate cells are still valid when the
cause 28 start HO message is received from the RAM process.
1.134
THR_RXQUAL_CAUSE_15 and EN_CAUSE_15 are not parameters but variables defined just after.
In B7:
New causes (26 & 27) introduced due to AMR support
Cause 26 is an emergency condition:
Intracell HO: speech codec from AMR-HR to AMR-FR
Cause 27 is a better condition
Intracell HO: speech codec from AMR-FR to AMR-HR
Causes 15 & 16 are modified due to AMR support
Specifics enablers and thresholds for AMR calls
AMR emergency HO (cause 26) is triggered if cause 15 or 16 has already been triggered
Cause 29 is created for intracell handover due to TFO
Codec sharing and optimization for MTM calls
Intracell HO
AV_RXQUAL_DL_HO > THR_RXQUAL_CAUSE_16 +
OFFSET_RXQUAL_FH
AND AV_RXLEV_DL_HO > RXLEV_DL_IH
AND EN_CAUSE_16 = ENABLE
AND [ no previous intracell handover for this connection
failed
OR EN_INTRACELL_REPEATED = ENABLE ]
Size of window for averaging quality: A_QUAL_HO
Size of window for averaging level: A_LEV_HO
1.135
THR_RXQUAL_CAUSE_16 and EN_CAUSE_16 are not parameters but variables defined after.
1.136
XX = UL or DL
For a non AMR call, the thresholds used are identical to the ones used for CAUSE 2 and CAUSE 4.
In this case and if EN_INTRACELL_REPEATED = DISABLE, when aN HO CAUSE 15 (or 16) fails, it can be modified
as UPLINK (or DOWLINK) QUALITY, HO CAUSE 2 (respectively HO CAUSE 4).
Principles:
Two consecutive encodings: speech coding and channel
coding
1.137
The main speech codec currently used in GSM networks, speech Full Rate, is quite old. It has been specified more
than 10 years ago. Around 1992, to increase network capacity, GSM has specified a half rate speech codec. But this
codec showed strong limitations in terms of speech quality, especially for mobile to mobile calls (double transcoding
degrades very much the speech quality of the half rate codec) and under poor radio conditions.
12.2
10.2
7.95
7.4 22.8 Kbit/s (FR TS)
6.7
11.4 Kbit/s (HR TS)
5.9 AMR HR 7.95 not supported
5.15
4.75
Audio Speech coding Channel coding Radio
Variable speech Variable channel
coding rate coding rate
1.138
In order to adapt the intermediate rate, a set of speech codecs has been defined by ETSI to be used by AMR:
When radio conditions are good, increases speech information.
When radio conditions are bad, protects speech information.
Full Rate: Alcatel implementation is fully compliant with GSM recommendations. All these AMR FR codec modes are
supported. In particular, the Alcatel BSS has implemented the 7.95, 5.9 and 4.75 codec modes which use polynomials
of constraint length 7 to ensure a high protection.
Half Rate: Alcatel implementation supports 5 out of 6 AMR HR codec modes (AMR HR 7.95 is not supported) which
are fully compliant with GSM recommendations. In particular, the Alcatel BSS has implemented the 4.75 codec mode
which uses polynomials of constraint length 7 to ensure a high protection.
During a call, only a subset out of these 8 codecs is used. The subset can include from 1 to 4 codecs. It is up to the
operator to define its own codec subset. In particular, he can define a codec subset limited to the common codec
modes supported by all the BSSs of its network (some BSSs may not be able to support all of them due to
implementability problems).
The codec subset defined by the operator is the same in the uplink and in the downlink.
1.139
The AMR principle is to have a set of codecs and, for any radio conditions, to use the one with the best speech quality.
Under good radio conditions, a codec with a high bit rate is used. Speech is encoded with more information so
the quality is better. In the channel coding, only little place is left for redundancy.
Under poor radio conditions, a codec with a low bit rate is chosen. Speech is encoded with less information, but
this information can be well protected due to redundancy in the channel coding.
The BSS adapts dynamically the codec in uplink direction and in downlink direction, taking into account the C/I
measured by the BTS (for uplink adaptation) and by the MS (for downlink adaptation).
The codec used in the uplink and used in the downlink can be different: the adaptation is independent in each direction.
This permits to use an optimal codec for each C/I value of each direction, as indicated in the figure below.
Speech
Quality
[dBQ]
or
[MOS]
C/I [dB]
The Codec mode can be modified on one frame out of two (CMI / CMC-CMR).
Decision based on thresholds (OMC-R settable), for the uplink and the
downlink C/Inorm
High
CODEC_MODE_4
(less robust)
AMR_FR_THR_3 + AMR_FR_HYST
AMR_FR_THR_3
CODEC_MODE_3
AMR_FR_THR_2 + AMR_FR_HYST
AMR_FR_THR_2
CODEC_MODE_2
AMR_FR_THR_1 + AMR_FR_HYST
AMR_FR_THR_1
CODEC_MODE_1
(most robust)
Low
1.141
Downlink adaptation
MS BTS TC
1.142
1.143
The metric used for codec mode adaptation is the evaluation of the ratio: signal over noise.
1.144
The main speech codec currently used in GSM networks, speech Full Rate, is quite old. It has been specified more
than 10 years ago.
Around 1992, to increase network capacity, GSM has specified a half rate speech codec. But this codec showed strong
limitations in terms of speech quality, especially for mobile to mobile calls (double transcoding degrades very much the
speech quality of the half rate codec) and under poor radio conditions.
A few years later, when GSM started to be introduced in North America, American operators asked for an improved
speech codec for full rate channels. Indeed speech quality was a major argument for customers used to have a good
speech quality with analog systems. For that issue, EFR was specified for GSM.
Recently, studies on AMR have been launched to provide a solution to:
Increase speech quality in full rate and half rate,
Increase network capacity by offering a good half rate solution,
Use a long-term solution, to avoid adding more and more codecs handled independently from the others,
Take into account Tandem Free Operation (TFO), especially between MSs on half rate on one side and on full
rate on the other side.
FR / HR discrimination
cell load AV_LOAD() computed from
load samples = NB_BUSY_TS / NB_TS * 100
non sliding window (LOAD_EV_PERIOD) averaging process
AV_LOAD()
100%
THR_FR_LOAD_U_SV1
= 80%
THR_FR_LOAD_U_SV3
=60%
THR_FR_LOAD_L_SV1 time
=50%
THR_FR_LOAD_L_SV3
=40%
1.145
The same computation is done to compute LOAD_SV3 with the thresholds: THR_FR_LOAD_U_SV3 and
THR_FR_LOAD_L_SV3 with the following relations:
THR_FR_LOAD_L_SV3 THR_FR_LOAD_U_SV3
THR_FR_LOAD_U_SV3 THR_FR_LOAD_U_SV1
THR_FR_LOAD_L_SV3 THR_FR_LOAD_L_SV1
Cause 26 is triggered if :
Current channel rate is HR
Current channel is dual rate and changes are allowed
AMR_FR speech codec is allowed:
EN_AMR_FR = ENABLE
1.146
1.147
1.148
Calculation of LOAD_SV3(0):
If previous value of LOAD_SV3 = false then
if AV_LOAD > THR_FR_LOAD_U_SV3 then
LOAD_SV3 = true
else
LOAD_SV3 = false
1.149
Cause 27 is triggered if :
1.150
1.151
Quality
HO cause 26 HO cause 27
THR_RXQUAL_CA_HIGH
THR_RXQUAL_CA_HIGH +
OFFSET_CA_HIGH
Full Rate Full Rate
HO cause 26
bad quality: 7
1.152
TC TC
TC TC
Codec GSM
(8 or 16 Kbit/s)
1.153
The Tandem Free Operation (TFO) feature is a way to avoid double transcoding in mobile to mobile speech calls.
Indeed without TFO, one GSM codec type is used between the first mobile and the first transcoder, then the speech is
transcoded into A/ law between transcoders and finally this speech is transcoded again into a second GSM codec
type (which may be the same as the first one) between the second transcoder and the second mobile.
With TFO, after call establishment, both BSSs at each side are able to negotiate a common GSM codec type which is
then used from one mobile to the other mobile. This negotiation is performed through in-band signaling between
transcoders.
MS TRAU TRAU MS
1.154
Exchange of codec
capabilities Intracell HO Normal operation
Exchange of codec
Codec match capabilities
TFO mode ON
1.155
1.156
1.157
Codec mismatch:
At call setup for a mobile to mobile speech call, when both BSSs do not use the same codec type, a codec
mismatch occurs. If a common codec type can be found, either one or possibly both BSSs perform an intracell
handover to use the common codec type found. Afterwards TFO can be started using this common codec type.
Codec mismatch resolution is authorized in the BSC using an O&M flag: EN_TFO_MATCH. This flag is
forwarded to the TC, via the BTS.
Codec optimization:
At call setup for a mobile to mobile speech call, it can occur that a first common codec type can be found but a
better speech quality would be provided with another common codec type. Once both BSSs operate in Tandem
Free, they exchange their complete codec capabilities, to try to find a better codec type than the current one.
Codec optimization is authorized in the BSC using an O&M flag : EN_TFO_OPT. This flag is forwarded to the
TC, via the BTS.
Classification of codec types :
In all cases, TFO is considered better as any tandeming configuration. In TFO, EFR is considered as better
than FR, considered as better than HR.
Force TFO vs. AMR :
TFO + AMR is not supported in this implementation of TFO. In the normal operation, a call established with
AMR will not initiate a TFO negotiation. The goal of the function Force TFO vs. AMR is to allow a call,
established with AMR to initiate a TFO negotiation and, if possible, to change of codec type to FR, HR or EFR
to establish TFO.
In-Path Equipments (IPEs):
TFO can only be activated if TFO frames (at 8 or 16 Kbit/s) can be sent transparently through the public
switching network. In-path equipments are equipments such as echo cancelers or A/ law converters that
modify the 64 Kbit/s speech signal. Such equipments need to be deactivated for TFO calls.
1.158
FORCE_TFO_VS_AMR:
TFO AMR not specified
Call setup in AMR is not followed by TFO negotiation
FORCE_TFO_VS_AMR enables HO cause 29 after
AMR call establishment towards best TFO codec
FORCE_TFO_HR_WHEN_LOADED:
Gives control on load regulation precedence vs. TFO
3 values: TFO_HR_NOT_FORCED, TFO_HR_ONLY,
TFO_HR_PREFERRED enable different behaviours in
case of loaded cell
Loaded cell Unloaded cell
MS / cell cap: HR/EFR/FR MS / cell cap: HR/EFR/FR
KEEP_CODEC_HO
keeps the same codec type in the new cell in case of internal intercell
HO in order to avoid resolving a new mismatch codec situation
Avoids double speech quality transition:
TFO --> non-TFO --> TFO
3 possible behaviors:
TFO_CALLS_ONLY: codec is preferably kept in case of internal
intercell HO for TFO calls only
ALL_CALLS: codec is preferably kept in case of internal intercell
HO for all calls (whatever the TFO state)
FREE: the choice of the codec type is free and depends on the
situation in the target cell
1.161
HANDOVER
PRIORITIES
HR to FR CHANNEL ADAPTATION
CAUSE 26 Intracell
UPLINK INTERFERENCE
CAUSE 15 Intracell
DONWLINK INTERFERENCE
CAUSE 16 Intracell
XXXXXXXXXXXXXXXXXXXXXXX
1.162
The causes 24, 12 and 23 have the same priority. Nevertheless, if a cell is a candidate for both causes, triggered in the
same time, it is kept only for cause 12.
Emergency causes
1- What is the HO cause 2?
2- Which is the flag to activate the HO
cause 2?
Time allowed:
45 minutes
1.163
Emergency causes
Complete the diagram below and fill in the chart with:
L_RXQUAL_UL_H = 3
RXLEV_UL_IH = -70 dBm
Nb of case --->
--- > 1 2 3 4 5 6
QUAL
AV_RXQ UAL_UL_HO 4 1 3 4 4 4
AV_RXLEV_UL_HO - 81 - 79 - 75 - 70 - 69 - 72
Current MS Power 33 33 33 33 33 29
(0,8 w) LEV
HO cause 2 : YES/NO ?
1.164
Nb of case ---> 1 2 3 4 5 6
AV_RXLEV_NCELL(n) - 70 - 70 - 80 - 70 - 70 - 75
AV_RXLEV_PBGT_HO - 80 - 70 - 75 - 75 - 79 - 96
PBGT(n)
HO cause 12: YES/NO ?
1.165
MS
Nb of case --->
--- > 1 2 3 4 5 6
AV_RXLEV_NCELL(n) - 70 - 70 - 80 - 70 - 70 - 75
AV_RXLEV_PBGT_HO - 80 - 70 - 75 - 75 - 79 - 96
PBGT(n) a only 10 0 -5 5 9 21
HO cause 12: YES/NO ? YES NO NO NO YES YES
PBGT > HO margin
PING_PONG_HCP=15 - > PBGT(n)
HO cause 12: YES/NO ?
1.166
No Ping-Pong margin
HO_MARGIN(0,n)=5 dB Ncell
DELTA_INC_HO_margin=5dB
1.167
Serving cell
MS
Number of case 1 2 3 4
AV_RXLEV_NCELL(n) -71 dBm -71 dBm -76 dBm -71 dBm
PBGT(n)
DELTA_HO_MARGIN(0,
n)
Cause 12 HO: YES/NO?
1.168
1.169
UL_QUAL 0 1 2 3 3 1 1 0 0 1
DL_QUAL 0 0 1 1 1 0 0 2 4 3
LOAD_SV3 false false false false true true true true true true
AV_RXQUAL_UL_CA_HR_FR
AV_RXQUAL_DL_CA_HR_FR
AV_RXQUAL_UL_CA_FR_HR
AV_RXQUAL_DL_CA_FR_HR
CHANNEL TYPE FR FR FR
1.170
capture HO (Cause 24 )
There are only 2W cells and 2W MS
L_RXLEV_CPT_HO(0,n) = -85dBm
EN_GENERAL_CAPTURE_HO = ENABLE
Ncell
Serving cell
Fill up the chart: MS
Nb of case --->
---> 1 2 3 4 5 6
AV_RXLEV_NCELL(n) - 70 - 70 - 80 - 70 - 70 -85
CAPTURE_TRAFFIC_CONDITION NOT_LOW HIGH ANY_LOAD HIGH HIGH HIGH
TRAFFIC_LOAD(0) HIGH LOW INDEFINITE HIGH LOW HIGH
TRAFFIC_LOAD(n) HIGH LOW INDEFINITE LOW LOW LOW
HO cause 24:
24: YES/NO
YES/NO ?
1.171
Neighbors 1 2 3
MS
1 -82 -85 -78
2 -79 -86 -92
3 -90 -82 -89
1.172
1.173
1.174
1.175
1.176
MS1 TFO?
1.177
MS1 TFO?
1.178
1.179
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Theoretical presentation
Radio measurements principles
Radio measurements data processing
Radio Link Supervision and Power control
Handover Detection
Handover Candidate Cell Evaluation
Handover Management
Exercise
1.180
BTS BSC
HO Preparation
Radio Active
Link HO Candidate
Channel HO Detection
Measurements Cell Evaluation
Pre-processing
HO
management
HO
protocol
MSC
Preprocess measurement
PBGT_FILTERING
CELLS EVALUATION PROCESS
HO_MARGIN_XX(0,n) Order or Grade
PRE-RANKING
1.181
The HO candidate evaluation process is run after all intercell handover alarms.
In case of intracell handover alarm (HO causes 10, 11, 13, 15, 16), the candidate cell evaluation process is skipped:
the target cell is the serving cell.
The handover detection gives as indication the raw cell list (built from book-keeping list) and the preferred layer for the
handover. In case of emergency handover alarms or cause 20 alarm, the cell evaluation will order the cells given in the
raw list, putting in the first position the cells belonging to the preferred layer, having the highest priority (if
EN_PRIORITY_ORDERING=ENABLE) and/or having the same frequency band type as the serving cell. In case of an
intercell handover alarm, if the serving cell belongs to the raw cell list (emergency handover from the DCS 1800 inner
zone of a multiband cell), this cell is put at the end of the candidate cell list with the MS zone indication OUTER.
In case of better condition handover alarms (except cause 20), the cell evaluation will order the cells given in the raw
list, putting in the first position the cells belonging to the preferred layer and having the highest priority (if
EN_PRIORITY_ORDERING=ENABLE).
Priority(0,n) = 0
Cell_layer_type Pref_layer
Priority(0,n) = 1
Priority(0,n) = 5
1.182
1.183
The filtering process allows to filter out cells from the target list before sending them to the ORDER or GRADE
evaluation process.
It can be enabled/disabled on-line on a per cell basis from the OMC-R with the flag EN_PBGT_FILTERING.
The candidate cells are filtered on their power budget in relation to a handover margin threshold based on the
handover cause.
Note: the averaging window used for this process is A_PBGT_HO (even for emergency handovers, where a handover
alarm could have been raised through A_LEV_HO or A_QUAL_HO samples)
Two types of cell evaluation algorithms can be used: ORDER and GRADE.
ORDER and GRADE are two different methods of cell ranking. They both consist in giving a mark or figure of merit to
each candidate cell.
The basic differences between ORDER and GRADE are that:
with ORDER
The candidate cell evaluation process interacts with the handover detection by use of cause-dependent
handover margins.
The candidate cell evaluation process takes into account the number of free TCHs in the candidate
cells.
with GRADE
The candidate cell evaluation process does not interact with the handover detection.
The candidate cell evaluation process takes into account the relative load of traffic channels in the
candidate cells.
The type of cell evaluation is chosen by the operator on a (serving) cell basis and is provided to the BSC with the
parameter CELL_EV.
For any handover cause, the first cell in the list is taken as a target cell, i.e. the cell with the highest value of
ORDER(n). The cells do not need to fulfil any other condition.
If no cell fulfils the condition and the serving cell does not belong to the target cell list, the target cell list is empty and
no further action is carried out.
LOADfactor(n) is a weighting factor that takes into account the relative load of
traffic channels in a cell
1.186
For any handover cause, the first cell in the list is taken as a target cell, i.e. the cell with the highest value of
GRADE(n). If no cell fulfils the condition and the serving cell does not belong to the target cell list, the target cell list is
empty and no further action is carried out.
Emergency HO detected
With the Candidate
evaluation.xls excel
sheet...
Filtering simulation for a
list of candidate cells
Ranking simulation for a
list of candidate cells
1- Book-keeping list
Time allowed:
15 minutes 1.187
Emergency HO detected
Averaging
2- measurement
?
3- PBGT Filtering
?
4- GRADE evaluation process
?
5- Target Cell
1.188
2.7 Exercise
1.189
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Theoretical presentation
Radio measurements principles
Radio measurements data processing
Radio Link Supervision and Power control
Handover Detection
Handover Candidate Cell Evaluation
Handover Management
Exercise
1.190
3 OTHER ALGORITHMS
1.191
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Program:
3.1 LCS
3.2 Dynamic SDCCH allocation
3.3 TCH resource allocation algorithm
3.4 MS Reselection algorithms
1.192
3 OTHER ALGORITHMS
3.1 LCS
1.193
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
LCS
Dynamic SDDCH allocation
MS Reselection algorithms
1.194
Mobile-based: The MS performs OTD signal measurements and computes its own location estimate. In this
case, the network provides the MS with the additional information such as BTS coordinates and the RTD values.
These assistance data can be either broadcast on the CBCH (using SMSCB function) or provided by the BSS in
a point-to-point connection (either spontaneously or on request from the MS).
Mobile-assisted: The MS performs and reports OTD signal measurements to the network and the network
computes the MSs location estimate.
With
OTD: Observed Time Difference: the time interval that is observed by an MS between the receptions of
signals (bursts) from two different BTSs.
RTD: Real Time Difference: This means the relative synchronization difference in the network between
two BTSs.
Finally, 4 methods are possible for positioning:
Cell ID+ TA,
This is the simplest method for determining the location of a mobile. It relies on the hypothesis that the
geographical coverage of a cell corresponds to that predicted by radio coverage studies. When an active
mobile is connected to a base station, the mobile is assumed to be located geographically within the area
predicted to be best served by this base station
Conventional (MS equipped with GPS System),
MS-based Assisted GPS,
MS-Assisted GPS.
Where is my son?
GPS reference OSP
Lb network
MS Abis Lh 3
SMLC
BTS SAGI
A-GPS
MFS server HLR
4. Paging, authentication,
ciphering, notification
8. Location LCS Client
3. Provide subscriber
response
location
BSC MSC GMLC
1. Location request
OSP
GMLC
5. Provide subscriber
positioning
6. Individual
HLR
SMLC
MFS
1.196
If the MS is in idle mode, the MSC first performs a CS paging, authentication and ciphering in order to establish an
SDCCH with the MS. The MS subscriber is not aware of it, i.e. no ringing tone, except towards GPRS MS in Packet
Transfer Mode which may suspend its GPRS traffic in order to answer to the CS Paging (i.e. not fully transparent for the
subscriber).
When the MS is in dedicated mode (after a specific SDCCH establishment for location, or during an on-going call), the
MSC sends the location request to BSC in the existing SCCP connection for the current call, which forwards it to the
SMLC
1.197
Send_Routing_Info rqst
Send_Routing_Info resp
Provide_Subscriber_Location
Paging
Authentication + Ciphering
.
BSSMAP Perform_Location_Request
BSSAP-LE Perform_Location_Request
Starts T_location
BSSAP-LE Perform_Location_Response
BSSMAP Perform_Location_Response
Stop T_location
Provide_Subscriber_Location Result
BSSMAP Clear Command and Release
LCS Service Response
1.198
The useful B8 content of the received PERFORM LOCATION REQUEST message is:
Location type,
Classmark information 3,
Requested QoS: provides service requirement concerning geographic positioning and response time
accuracy, the response time category (Low Delay or Delay Tolerant),
Current Cell Id + TA information are always provided to the SMLC.
The time of transfer of the assitance data on the SDCCH is estimated about 14s for a 1000 octets information,
Di
Ma n giv
rec azimu
the
in
tio
Be n by
am
m
e
th
553
Site Geographical
Information
(Lat/Long)
TA
A
MS Estimated
Location
1.199
With the TA positioning method, no signalling exchange is required between the SMLC and the MS (i.e. RRLP protocol
is not required). The TA positioning method is applicable to all the MSs (supporting LCS or not).
Based on:
Cell Identity (CI) of the serving cell and
Timing Advance (TA) value reported by MS
intersection point of a line from the BTS antenna in their main direction with a circle which radius is
corresponding with the propagation delay (timing advance) is the MS estimated position
Omni-directional cells: MS position = site position
Parameters:
EN_LCS flag to enable/disable the Location Services per BSS
0 = Enabled; 1= Disabled; Default = 0
IF EN_LCS=1, CI+TA method is enabled in all the BSS cells
LCS_LATITUDE
Latitude of the BTS supporting the cell
LCS_LONGITUDE
Longitude of the BTS supporting the cell
LCS_AZIMUTH
Antenna direction orientation for the sector supporting the cell
HALFPWR_BEAM_WIDTH
Antenna half power beamwidth for the sector supporting the cell
Optimization parameters:
ARC_SIZE_FACTOR
Factor used in the computation of the width in degree of the ellipsoid arc returned by the MFS when
computing location estimate based on TA positioning method.
MIN_RADIUS_FACTOR
Factor used in the computation of the minimum radius of the ellipsoid arc returned by the MFS when
computing location estimate based on TA positioning method
MAX_RADIUS_FACTOR
Factor used in the computation of the maximum radius of the ellipsoid arc returned by the MFS when
computing location estimate based on TA positioning method
Perform
Location Response (X,Y)
(X,Y) : Computed position
1.200
Assistance data gathered from a GPS reference network receiver is broadcasted to the GPS MS
Flags/Parameters
EN_LCS = 1
EN_MS_BASED_AGPS enables/disables the positioning method MS Based A-GPS per CELL
0 = disabled; 1 = enabled; default = 0
EN_MS_ASSISTED_AGPS enables/disables the positioning method MS Assisted A-GPS per CELL
0 = disabled; 1 = enabled; default = 0
MS BTS A-GPS
BSC SMLC
Server
Perform
Location Request GPS info Location Request
Request
GPS info
Assistance Data
Assistance Data Response
Position Response
Measurement Position Request
Location Response
Measurement Position Response (X,Y)
(X,Y)
Perform
(X,Y) Location Response
POSITIONING CALCULATION
latitude, longitude (and
altitude)
(X,Y) : Computed position
1.202
Using assistance data, MS computes by itself the position and sends it back to the SMLC
MS BTS A-GPS
BSC SMLC
Server
Perform
Location Request GPS info Location Request
Request
GPS info
Assistance Data
Assistance Data Response
Position Response
Measurement Position Request
Location Response
Pseudo-range Measurement Position Response (M) GPS Location
MEASUREMENTS Request (M)
GPS Location
Perform Response (X,Y)
(X,Y) Location Response
(X,Y)
Using a reduced set of assistance data, the MS makes pseudorange measurements and sends the result
to the A-GPS server, which fixes the position in the end
HO preparation
Inhibition of better cell handovers
Other HO
MS BTS BSC SMLC MSC GMLC HLR LCS Client
Send_Routing_Info rqst
Send_Routing_Info resp
Provide_Subscriber_Location
Paging
Authentication + Ciphering
.
BSSMAP Perform_Location_Request
BSSAP-LE Perform_Location_Request
Starts T_location
BSSLAP - Reset
EMERGENCY HO
DETECTION
1.204
HO management
Internal HO
MS BTS BSC SMLC MSC GMLC HLR LCS Client
INTRA BSC HO
On going
.
BSSMAP Perform_Location_Request
BSSAP-LE Perform_Location_Response
BSSLAP-Reset
1.205
Mobile in communication
HO management
external HO
BSSAP-LE Perform_Location_Abortt
BSSAP-LE Perform_Location_Response
BSSAP-LE Perform_Location_Response
1.206
FLAGS Timers
EN_LCS
T_Location
EN_SAGI
T_Location_longer
T_Loc_Abort
OPTIMIZATION DATA T_LCS_delay_tolerant
T_LCS_LowDelay
ARC_SIZE_FACTOR T_RRLP_low_delay
MIN_RADIUS_FACTOR T_RRLP_delay_tolerant
MAX_RADIUS_FACTOR
1.207
BSS PARAMETERS
EN_LCS (BSC)
Flag which enables or disables the LCS feature in the BSS.
EN_SAGI
Flag indicating whether SAGI is configured or not for this BSS
T_Location:
BSC timer on a per call basis to guard the response from the SMLC in case of Location Request, when no
RRLP exchange is triggered with the MS.
T_Location_longer:
BSC timer on a per call basis to guard the response from the SMLC in case of Location Request, when an
RRLP exchange is triggered with the MS. Replace T_Location timer in case of Conventional GPS, MS-
Assisted A-GPS, MS-Based A-GPS.
T_Loc_Abort
BSC timer to guard the response from the SMLC in case of Location Abort.
T_LCS_LowDelay
SMLC timer to guard the calculation of the MS position (including the RRLP message exchange
with the target MS) in case of a Low Delay Location Request.
T_LCS_DelayTolerant
SMLC timer to guard the calculation of the MS position (including the RRLP message exchange
with the target MS) in case of a Delay Tolerant Location Request.
T_LCS_LowDelay
SMLC timer to guard the calculation of the MS position (including the RRLP message exchange
with the target MS) in case of a Low Delay Location Request.
T_RRLP_Low_delay
Timer to guard the RRLP exchange between the SMLC and the MS .
T_RRLP_delay_tolerant
Timer to guard the RRLP exchange between the SMLC and the MS.
Optimization data:
ARC_SIZE_FACTOR
Factor used in the computation of the width in degree of the ellipsoid arc returned by the MFS when
computing location estimate based on TA positioning method.
MIN_RADIUS_FACTOR
Factor used in the computation of the minimum radius of the ellipsoid arc returned by the MFS when
computing location estimate based on TA positioning method
MAX_RADIUS_FACTOR
Factor used in the computation of the maximum radius of the ellipsoid arc returned by the MFS when
computing location estimate based on TA positioning method
Alcatel University - 8AS902001485 VH ZZA Ed.02 Page 1.207
3.1 LCS
B8 Cell Parameters
EN_CONV_GPS
EN_MS_ASSISTED_AGPS LCS_LATITUDE
EN_MS_BASED_AGPS LCS_LONGITUDE
LCS_SIGNIFICANT_GC
LCS_AZIMUTH
HALF_POWER_BANDWIDTH
1.208
CELL PARAMETERS
EN_CONV_GPS
Flag to enable/disable the Conventional GPS positioning method.
EN_MS_ASSISTED_AGPS
Flag to enable/disable the MS Assisted A-GPS positioning method.
EN_MS_BASED_AGPS
Flag to enable/disable the MS Based A-GPS positioning method.
LCS_LATITUDE
Latitude of the BTS supporting the cell (used by the MFS to compute location estimate based on TA
positioning method).
LCS_LONGITUDE
Longitude of the BTS supporting the cell (used by the MFS to compute location estimate based on TA
positioning method).
LCS_SIGNIFICANT_GC
Indicates whether latitude and longitude are significant or not
LCS_AZIMUTH
Antenna direction orientation for the sector supporting the cell (used by the MFS to compute location
estimate based on TA positioning method).
HALF_POWER_BANDWIDTH
Half power beam width of the antenna for the sector supporting the cell (used by the MFS to compute
location estimate based on TA positioning method).
Remark: To have LCS supported for a cell, the operator must activate LCS on the BSS handling this cell but he
must also activate GPRS for this cell (i.e. setting of MAX_PDCH to a value > 0, the cell being kept locked for
GPRS if the operator does not want to have GPRS running on this cell) and configure all the required
transmission resources (Ater and Gb resources) on the GPU(s) connected to this BSC
1.209
3 OTHER ALGORITHMS
1.210
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
LCS
Dynamic SDDCH allocation
MS Reselection algorithms
Static Min
SDCCH
time slots
TCH
Capacity
1.211
Definitions
A Static SDCCH timeslot is a physical timeslot fixed allocated on the air interface. It contains 3, 4, 7 or 8 SDCCH sub-
channels depending on whether the timeslot is an SDCCH/3, SDCCH/4, SDCCH/7, or SDCCH/8 timeslot.
Principles
Too few SDCCH time slots could result in high blocking rate
on SDCCH (Configuration 1)
Too many SDCCH time slots could lead to a lack of TCH
resources (Configuration 2)
Configuration 1 Configuration 2
SDCCH SDCCH
time slots time slots
TCH TCH
Capacity Capacity
1.212
Definition
An SDCCH is a logical SDCCH sub-channel mapped on a Static SDCCH timeslot or a Dynamic SDCCH/8 timeslot.
+ BCC
TCH
SDD
SDC
SDC
TCH
TCH TCH TCH TCH TCH TCH
TCH
SDD TCH TCH TCH TCH TCH TCH TCH
BCC: BCCH
SDC: Static SDCCH
1.213
The location of the Dynamic SDCCH/8 time slots are fixed by O&M configuration.
SDCCH
Pure SDCCH or static SDCCH
TCH
Pure TCH
TCH/SDCCH
dynamic SDCCH
TCH/SPDCH
MPDCH
1.214
The OMC-R provides the BSC with the following O&M type of radio timeslots:
Main BCCH timeslot (BCC): It is a timeslot carrying FCCH + SCH + BCCH + CCCH.
Main combined BCCH timeslot (CBC): It is a timeslot carrying FCCH + SCH + BCCH + CCCH +
SDCCH/4 + SACCH/4.
Static SDCCH timeslot (SDC): It is a timeslot carrying SDCCH/8 + SACCH/8.
Dynamic SDCCH/8 timeslot (SDD): It is a timeslot carrying TCH + SACCH or SDCCH/8 + SACCH/8
TCH timeslot (TCH): It is a timeslot carrying TCH + SACCH or PDCH
A pure SDCCH timeslot can carry x SDCCH sub-channels where x equal to:
4 in case of combined CCCH and when CBCH is not configured on the timeslot,
7 in case of non-combined CCCH and when CBCH is configured on the timeslot,
3 in case of combined CCCH and when CBCH is configured on the timeslot,
8 for a normal SDCCH timeslot.
When allocated as SDCCH, a TCH/SDCCH timeslot can carry up to 8 SDCCH sub-channels.
Are they any free SDCCH Are they any free SDCCH Are they any Dynamic
sub-channel among Static sub-channel among Dynamic SDCCH/8 timeslots available
SDCCH timeslots ? SDCCH/8 already allocated ? and free in the cell ?
No No Yes
? ? ? Allocate
Yes Yes No
one dynamic
1.215
TS with
Pure SDCCH LOWEST TCU
LOAD
Timeslots
TS with
MAXIMUM FREE
TCH/SDCCH SDCCH Sub
TS allocated as channels
SDCCH
TS on FR
TRX
TCH/SDCCH
allocated as TCH
TS with lowest
index on TRX
with lowest
TRX_ID
1.216
Note that a SDCCH request can not access the timeslots reserved by NUM_TCH_EGNCY_HO. If all remaining
TCH/SDCCH timeslots are reserved by NUM_TCH_EGNCY_HO, then the SDCCH request shall be rejected.
? started
No
Yes
T_DYN_SDCCH_HOLD
No
running ? Yes
? T_DYN_SDCCH_HOLD ?
Yes Expires ?
No
T_DYN_SDCCH_HOLD TCH/SDCCH
stopped deallocated
1.217
3 10
4 7 1 8 5
2 9 6 11
12
1.218
1.219
Note1: For one TRX, dynamic SDCCHs are over-dimensioned because of the granularity of 8. According
to the Alcatel traffic model, all dynamic SDCCHs will not be used.
Note2: An additional dynamic SDCCH/8 must be provided for each DR TRX (these are expected mainly
on small cells).
rules:
At least one static SDCCH/4 or SDCCH/8 on BCCH TRX
Up to 24 static/dynamic SDCCH sub-channels per TRX
Up to 32 static/dynamic SDCCH sub-channels per TCU
Up to 88 static/dynamic SDCCH sub-channels per CELL
1.220
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
LCS
Dynamic SDDCH allocation
MS Reselection algorithms
1.221
1.222
The operator has to choose between a Combined BCCH (CBC TS) or a Non-combined BCCH configuration (BCC TS).
SDD TS can carry either TCH or SDCCH channels but not both at the same time.
TCH TS can carry either CS traffic channel TCH or PS logical channels but not both at the same time.
In the BSS the RAM software module maps the OMC-R cell radio
configuration to its own types of TS :
Pure BCCH timeslot: BCC TS carrying only common CS
signalling (BCCH+CCCH)
Pure SDCCH timeslot: CBC or SDC TS carrying only
dedicated CS signalling (SDCCH)
Pure TCH timeslot: TCH TS carrying only TCH traffic
TCH/SDCCH timeslot: SDD TS carrying either CS traffic
(TCH) or dedicated CS signalling (SDCCH)
TCH/SPDCH timeslot: TCH TS carrying either CS traffic
(TCH) or PS traffic (SPDCH channels)
MPDCH timeslot: TCH TS carrying common PS signalling
(PBCCH+PCCCH or PCCCH only)
1.223
TCH/SDCCH timeslots are allocated as TCH or SDCCH according to an SDCCH dynamic allocation algorithm
presented in the Introduction to Radio Fine Tuning B8 training course.
TCH/SPDCH timeslots are allocated as TCH or SPDCH according to a SPDCH dynamic allocation algorithm presented
in the Introduction to GPRS & E-GPRS Quality of Service Monitoring B8 training course.
SDC
SDD TCH/SDCCH
TCH TCH/SPDCH
MPDCH
Pure TCH
MPDCH TS are defined on the BCCH TRX even if the corresponding TRX_PREF_MARK is different than 0.
1.225
The timeslots shall be consecutive on a given TRX means that there shall be no hole in the SPDCH group.
If several SPDCH groups can be defined on the same TRX and having the same number of consecutive timeslots then
the group that is located on the left side of the TRX (i.e. the timeslots having the lowest index) shall be chosen.
0 TRX2 SDD
SDC TCH SDC TCH TCH TCH TCH TCH
The timeslots shall be consecutive on a given TRX means that there shall be no hole in the SPDCH group.
If several SPDCH groups can be defined on the same TRX and having the same number of consecutive timeslots then
the group that is located on the left side of the TRX (i.e. the timeslots having the lowest index) shall be chosen.
1.227
A DR TS (timeslot on a DR TRX) is free if no FR TCH or HR TCH is allocated for a call on this timeslot.
A DR TS is busy if at least one TCH is allocated for a call on this timeslot:
1 FR TCH
or 1 HR TCH (HR 0 TCH or HR 1 TCH)
or 2 HR TCHs (HR 0 TCH and HR 1 TCH)
1.228
TCH request
radio capability of the mobile
cell channel type capability
channel type (FR,HR,DR)
cell codec type capability
cell load speech version (FR, HR, EFR, AMR FR, AMR HR)
request type (NA or HO)
TCH allocation
no yes
TCH free?
NUM_TCH_EGNCY_HO
T_QHO TCH allocation
ALLOC_ANYWAY
T11 no yes
TCH free?
T11_ FORCED
1.230
The BSS selects the TCH sub-pools in which a TCH channel can
be allocated according to:
the requested channel rate and the cell load situation
favour HR if cell is loaded
a priority given to generic resources
1. G1 pool (E-GSM mobile only)
2. GSM/DCS pure TCH - TCH/SPDCH pool
3. GSM/DCS TCH/SDCCH pool
an optimisation of FR/HR resources
favour FR pool over DR pool for a FR TCH request
favour HR pool over DR pool for an HR TCH request
the availability of a TCH channel in the sub-pool
1.231
favour G1 pool for an E-GSM mobile (penetration of E-GSM mobile is low and GSM/DCS traffic is high)
disfavour TCH allocation on TCH/SDCCH TS (favour signalling over traffic)
1.232
TCH candidates
Highest Biggest Best
of the selected
TRX_PREF_MARK Mobile Allocation Interference Band
TCH sub-pool
HR 0 Highest Highest
Selected TCH
TCH sub-channel TS index TRX identity
FR allocation
or HR allocation on busy TS
1.233
The BSS attempts to offer the best quality of service for TCH calls in accordance with the privileged order between the
groups of TRXs (if any) defined by the operator. Among a group of TRXs the BSS attempts to allocate traffic channels
that have the best quality characteristics (channels using frequency with low reuse factor, large hopping frequency
sets, low measured interference).
The benefits from this type of allocation are that the operator has the possibility to define groups of TRXs and to favour
(or to disadvantage) them on the other if he wants to do so. Among a group of pure TCH or TCH/SDCCH timeslots, the
overall interference is kept as low as possible, thus the user will perceive a better quality of service.
The BSS chooses the best TCH among the sub-channels of the selected TCH sub-pool applying criteria below in the
specified order of priority:
TCH candidates
Highest Highest HR 0
of the selected Selected TCH
TRX rank TS index TCH sub-channel
TCH sub-pool
FR allocation
or HR allocation on busy TS
1.234
The BSS tends to allocate to the MFS the TCH/SPDCH timeslots so as to avoid conflicts between CS and PS
allocations on PS capable TRX.
In order to be able to allocate as much slave PDCHs as possible to a given TBF, it is important to avoid any mix of
allocation between TCHs and SPDCHs (e.g. avoid on a TRX a configuration such as TCH TCH SPDCH SPDCH
TCH SPDCH SPDCH SPDCH). For that purpose, a TRX rank is assigned to each PS capable TRX. The TRX
having the highest TRX rank is preferentially selected for TCH allocations, whereas TRX having the lowest TRX rank is
preferentially selected for SPDCH allocations
This rule only applies on PS capable TRX. On a given PS capable TRX, TCH are preferentially allocated on the right
side of the TRX (highest TS index), whereas SPDCH are preferentially allocated on the left side (lowest TS index).
TRX_PREF_MARK 0 1 2 3 4 5 6 7 TRE
0 TRX2 SDD
SDC TCH TCH TCH TCH TCH TCH TCH G4 MP DR
Time allowed:
10 minutes
1.235
TRX_PREF_MARK 0 1 2 3 4 5 6 7 TRE
0 TRX1 G4 MP FR
0 TRX2 SDC G4 MP DR
1 TRX3 G3 DR
0 TRX4 G4 MP FR
1 TRX5 G3 DR
1.236
2 TRX1 P P P GSM/FR
3 TRX2 SDC
TSD P P P P H F GSM/DR
- TRX3 F F F F F F GSM/DR
1 TRX4 P P P P P P P GSM/FR
- TRX5 H H H H F H F H H G1/DR
1.237
1.238
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
LCS
Dynamic SDDCH allocation
MS Reselection algorithms
1.239
Idle mode
Status null:
the mobile station (MS) is off
Status search BCCH:
the MS searches a broadcast channel with the best signal level (cell selection and reselection)
BCCH list: up to 36 BCCH frequencies plus BSIC can be saved on SIM per visited network.
Look if frequencies of the BCCH list can be used.
No entries in the BCCH list, or the location is completely different: scan frequency band.
Status BCCH:
the MS is synchronized on a BCCH. The MS camps on a cell.
The BTS sends the neighbor cells list (BCCH allocation BA) on BCCH in System Information (SI) 2, 2bis
and 2ter if BSS parameter EN_INTERBAND_NEIGH in dual band networks:
GSM900 serving cell
- GSM900 neighbor cells put into SI 2
- GSM1800 neighbor cells put into SI 2ter/2bis
GSM1800 serving cell
- GSM900 neighbor cells put into SI 2ter
- GSM1800 neighbor cells put into SI 2/2bis
The MS measures RXLEV from BCCH of the serving and neighbor cells.
Camping on a cell is performed using C1 criteria only (the chosen cell is the one with the best C1)
The MS needs to have access to the network.
The MS needs to be accessible by the network.
Reselection is done using the mechanisms referenced above
handover algorithms in idle mode
C1
ensure that, if a call was attempted, it would be done with a
sufficient downlink and uplink received level
based on 2 parameters, broadcast on BCCH
RXLEV_ACCESS_MIN [dBm]
minimum level to access the cell
MS_TXPWR_MAX_CCH [dBm]
maximum level for MS emitting
1.240
C1
evaluated every 5 sec (minimum)
C1 = A - MAX(0,B) > 0
A = RxLev - RXLEV_ACCESS_MIN
assess that the MS received level is sufficient
B = MS_TXPWR_MAX_CCH - P
P maximum power of MS
assess that the BTS received level will be sufficient
if MS_TXPWR_MAX_CCH < P
If A > 0 & B < 0 OK, if B > 0, it can be compensated by A
A >> 0 means that the MS is closer to the BTS
1.241
C2
CELL_RESELECT_PARAM_IND= not present THEN C2=C1 else
C2 = C1 + CELL_RESELECT_OFFSET - TEMPORARY_OFFSET (T)
(if PENALTY_TIME 31)
if T > PENALTY_TIME, TEMPORARY_OFFSET(T) = 0
used to avoid locating on transient cell
CELL_RESELECT_OFFSET used to favor cell among other (e.g.
micro-cell vs. umbrella, once T > PENALTY_TIME)
Or C2 = C1 - CELL_RESELECT_OFFSET
(if PENALTY_TIME = 31)
CELL_RESELECT_OFFSET used to handicap some cells among
others
One reselection criterion is compared to C2s
C2neighbor > C2current if cells belong to same LA
C2neighbor > C2current+Cell_Reselect_Hysteresis if cells from a
different LA
1.242
Note:
CRO: from 0 to 126 dB, step 2dB
PENALTY_TIME: from 1=20s to 30=600s, step: 20s; 31=infinite
TEMPORARY_OFFSET: from 1=10dB to 6=60dB; 7 = infinite
The use of a second formula (Penalty_time = 31) is restricted to very special cases, as we do not like to penalize a cell.
If a cell is parametered with PT=31, it will be penalized compared to ALL its neighbors. To penalize a cell compared to
one neighbor, one should better boost the neighbor cell (using the first formula).
The first formula is very useful for favoring indoor cell or microcell.
CI=6169
GSM900
CI=6270
(8564,6169) Cell 1
(8564, 1964)
1.244
1.245
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
1.246
1.247
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Theoretical presentation
Examples and Exercises
SESSION OBJECTIVES
JUSTIFICATION
Three Example/Exercises
1.248
1.249
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Theoretical presentation
Examples and Exercises
1.250
Call drop
HO/Call
1.251
1.252
7 7
6 6
samples 5
3
5
2 2
0
1
600 1000
800
400 600
200 400
200
activated 0
2
S ta n d a rd D e vi a ti o n
3
0
S ta n d a rd D e vi a ti o n
1 .5
2
1
1
0 .5
0 0
Never forget that Abis information takes into account the traffic distribution in the cell. Any parameter tuning done after
an Abis study has to be checked periodically as the distribution in the cell can change from one week to another.
Use the pivot table function (Excel) to build this graph.
RxQUAL
RxQUAL
0
10
08
06
04
02
00
8
6
4
2
0
8
6
4
2
0
8
6
4
2
0
8
6
4
2
0
8
6
4
2
0
8
-9
-9
-9
-9
-9
-8
-8
-8
-8
-8
-7
-7
-7
-7
-7
-6
-6
-6
-6
-6
-5
-5
-5
-5
-5
-4
-1
-1
-1
-1
-1
-1
1.254
A_LEV_HO ? ? 4
1.255
1.256
1.257
In the example below, a dynamic MS PC is activated. The MS power changes are really reactive and control the UL
level between -80 and -90dBm. In this example, the HO threshold is -98 dBm.
RxLev_UL
1 39 77 115 153 191 229 267 305 343 381 419 457 495 533 571 609 647 685 723 761 799 837 875 913 951 989 1027
-70
-75
-80
-85 RxLev_UL
-90
-95
-100
33
31
29
27
25
23 MS_PwrLevel
21
19
17
15
13
1 40 79 118 157 196 235 274 313 352 391 430 469 508 547 586 625 664 703 742 781 820 859 898 937 976 1015
Time allowed:
5 minutes
1.258
1.259
Fast Traffic HO
Useful in case of sudden traffic peaks as the process
response is instantaneous (no averaging window)
The principle is to force handover towards neighbor cells
which have lower traffic when a request is queued in the
serving cell.
Interaction with Forced DR due to the use of same
thresholds
Optimization method (repetitive process)
Tunes L_RXLEV_NCELL_DR(n), FREElevel_DR(n)
Applies new values, checks traffic peaks, QoS
indicators
1.260
DELTA_HO_MARGIN (0,n)
CHANGE DYNAMICALLY TRAFFIC DISTRIBUTION WITH HO:
Traffic HO Cause 23
Ease outgoing better condition HO on a traffic point of
view
Slow down outgoing better cell HO (to be tuned for a given
couple of cells)
When the better cell in radio condition is the worst cell
in traffic terms
Optimization method (repetitive process)
Tune DELTA_DEC_HO_MARGIN and
DELTA_INC_HO_MARGIN
Apply new values, check traffic, QoS indicators and
possibly speech quality
1.262
1.263
HO_MARGIN / LINK_FACTOR
CHANGE STATICALLY TRAFFIC DISTRIBUTION WITH HO:
Ease outgoing better cell HO (to be tuned for a given couple
of cells)
Decrease HO_MARGIN (can make a cell candidate)
Increase LINK_FACTOR (used to rank candidate cells)
Optimization method (repetitive process)
Look for neighbor cells able to carry extra traffic
Use Abis trace to check if these cells are candidate
if yes, use LINK_FACTOR to favor them
if not, use HO_MARGIN and LINK_FACTOR
Apply new values, check traffic, QoS indicators and
possibly speech quality
1.264
1.265
FREE_FACTOR/LOAD_FACTOR
Taking into account the current load of cells, send the MS toward the less
loaded cell with HO
Ease outgoing better cell HO, according to
Load_Factor (% of TCH occupancy) of serving and target cells
Free_Factor (number of free TCHs) of serving and target cells
(order only)
cannot make a candidate cell, only change ranking
Tuning method (repetitive)
to be activated locally for each cell with default parameter setting
look for QoS indicators (esp. traffic intensity and blocking rate)
tune tables accordingly
1.266
1.267
1.268
cell 1 : 24
cell 2 : 45 cell 3 : 23
1.269
1.270
PBGT(0)=PBGT(n)=
Cause 12 Cause 12
0
EN_TRAFFIC_HO = 0
PBGT(0) = 5 PBGT(n) = 5
5 minutes
1.271
PBGT(0)=PBGT(n)=0
Queued Ass Req Av_Rxlev_Ncell(n) = -82dBm Av_Rxlev_Ncell(0) = -74dBm
Av_Rxlev_PBGT_HO = -82dBm
L_RLEV_NCELL_DR(n) = -85dBm
PBGT(0) = 5 PBGT(n) = 5
Time allowed:
5 minutes
1.272
PBGT(n) = -1
PBGT(0) = 9
PBGT(0) = 5
Time allowed:
5 minutes
1.273
1.274
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
1.275
1.276
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Theoretical presentation
TUNNEL Case
RADAR Case
TOWER Case
RESURGENCE Case
FOREST Case
HIGHWAY Case
TCH/SDCCH CONGESTION Case
INDOOR CELL CONGESTION Case
SESSION OBJECTIVES
JUSTIFICATION
DETAILED PROGRAM
1.277
1.278
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Theoretical presentation
TUNNEL Case
RADAR Case
TOWER Case
RESURGENCE Case
FOREST Case
HIGHWAY Case
TCH/SDCCH CONGESTION Case
INDOOR CELL CONGESTION Case
Outdoor
Pedestrian
BTS
mobile
1.279
1.280
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Theoretical presentation
TUNNEL Case
RADAR Case
TOWER Case
RESURGENCE Case
FOREST Case
HIGHWAY Case
TCH/SDCCH CONGESTION Case
INDOOR CELL CONGESTION Case
Radar situation
A radar cell situated on top of a hill provides a wide coverage area.
An industrial zone in the valley is covered by small cells but also by the
radar cell. The serving areas in the IZ are not clearly defined.
Objective
Give a parameter set to prevent the radar cell from catching any traffic
in the industrial zone by HO assignment
1.281
1.282
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Theoretical presentation
TUNNEL Case
RADAR Case
TOWER Case
RESURGENCE Case
FOREST Case
HIGHWAY Case
TCH/SDCCH CONGESTION Case
INDOOR CELL CONGESTION Case
Tower situation
The indoor mobile selects in idle mode the outdoor cell (same LA)
Objective Indoor
Antenna
Define a set of parameters to avoid that effect
BS1
1.283
1.284
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Theoretical presentation
TUNNEL Case
RADAR Case
TOWER Case
RESURGENCE Case
FOREST Case
HIGHWAY Case
TCH/SDCCH CONGESTION Case
INDOOR CELL CONGESTION Case
Resurgence situation
In rural network, especially in hilly landscape, many resurgences occur
from very far cells.
Objective
Define a set of parameters to avoid radio link establishment to those
cells and TCH traffic on those cells
Cell A
Cell B
Resurgence
from cell A
25 km
1.285
1.286
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Theoretical presentation
TUNNEL Case
RADAR Case
TOWER Case
RESURGENCE Case
FOREST Case
HIGHWAY Case
TCH/SDCCH CONGESTION Case
INDOOR CELL CONGESTION Case
Forest
ATT=10dB every 100m
-75dBm -90dBm
Highway
BTS
1.287
1.288
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Theoretical presentation
TUNNEL Case
RADAR Case
TOWER Case
RESURGENCE Case
FOREST Case
HIGHWAY Case
TCH/SDCCH CONGESTION Case
INDOOR CELL CONGESTION Case
Highway situation:
A highway is slightly covered (best coverage on 200m) by an
orthogonal cell (cell C on the map)
Objective
Define a set of parameters to avoid traffic in the orthogonal cell
Cell C
Cell B
Cell A
1.289
1.290
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Theoretical presentation
TUNNEL Case
RADAR Case
TOWER Case
RESURGENCE Case
FOREST Case
HIGHWAY Case
TCH/SDCCH CONGESTION Case
INDOOR CELL CONGESTION Case
Cell B Cell A
LA2 LA1
LA frontier
1.291
1.292
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Theoretical presentation
TUNNEL Case
RADAR Case
TOWER Case
RESURGENCE Case
FOREST Case
HIGHWAY Case
TCH/SDCCH CONGESTION Case
INDOOR CELL CONGESTION Case
1.293
1.294
1.295
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
1.296
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Erlang B law
Frequency hopping influence on PCHO process
Load & Traffic evaluation
Training exercises solutions
Example:
1 TCH is observed during 1 hour
one can observe 1 call of 80 sec and 1 call of 100 sec
the observed traffic is T = (80+100)/3600 = 0.05 ERLANG
1.297
ERLANG COMPUTATION
TCH = (350 * 85)/3600 = 8.26 ERLANG
SDCCH = [ (350 + 350*3) * 4.5 ] / 3600 = 1.75
ERLANG
1.298
ERLANG B LAW
relationship
between
offered traffic ca ll/se cond
ca ll/se cond
10
number of
10
9
9
resources 8
8
blocking rate
7
6
6
5
5
4
4
In a telecom system, 3
2
3
1
1
13
17
21
25
29
33
37
41
45
49
53
57
61
65
69
73
77
81
85
89
93
97
0
1
13
17
21
25
29
33
37
41
45
49
53
57
61
65
69
73
77
81
85
89
93
97
LAW
1.299
The graph gives the number of connection requests per second during 35 seconds.
P b lo c k = N!
N: number of resources N
E
k
k =0 k!
E: offered traffic [Erlang]
1.300
Using Abacus
1.301
Example:
1.302
1.303
CELL DIMENSIONING
1.304
CELL DIMENSIONING
Channels (12;2%) = 19
1.305
1.306
1.307
1.308
TRAINING EXERCISE
Complete this form in order to get less than 2% of blocking in all cases.
cell call mix info Erlang TCH traffic forecast proposed config
Offered traffic
12, 743 450 call/hour 10.08 Erlang TCH 30 % offered traffic 13.1 Erlang TCH - > 20 TCH
mean TCH call duration : 80 increase 3 TRX
sec
blocking rate TCH : 0.8%
Back
1.309
cell call mix info Erlang TCH traffic forecast proposed config
12, 743 450 call/hour 10 Erlang TCH 30 % TCHincrease 13,1 Erlang TCH- >20
mean TCHcall duration : 80 TCH
sec (450*80)/3600 10,081*1.3=13.1
blocking rate TCH: 0.8% =10 3 TRX
10/.992=10.08
1
12,675 330 call/hour (330*129)/360 30 % TCHincrease 16 Erlang TCH->24 TCH
mean TCHcall duration 129 0
sec =11.825/0.96 12.3177*1.3 =16 4 TRX
blocking rate 4% =12.3177
12,865 600 call/hour (600*96)/3600 30 % TCHincrease 22.6 Erlang TCH->31 TCH
mean TCHcall duration 96 =16/.92 =17.4
sec 17.4*1.3 =22.6 5 TRX
blocking rate 8 %
1.310
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Erlang B law
Frequency hopping influence on PCHO process
Load & Traffic evaluation
Training exercises solutions
Frame Voice
DECODER Deinterleave Erasure
DEMOD Decoder
Error correct. Decision
- ENCODER
1.311
correlated
1.312
0,6 1,00%
0,4
0,50%
0,2
0 0,00%
Cycli
Random
Ref
1.313
Conclusion
When frequency hopping is activated
We can accept in Power Control and Handover
processes, a threshold increase:
OFFSET_HOPPING_PC and
OFFSET_HOPPING_HO
Back
1.314
1.315
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Erlang B law
Frequency hopping influence on PCHO process
Load & Traffic evaluation
Training exercises solutions
Back
Cause 12
Back
Cause 26
1.316
1.317
1.318
LOADfactor determination:
LOADlevel in %
LOADfactor in dB
1.319
FREEfactor determination:
1.320
Nb free TCH FREEfactor Load = (1-Nb free TCH/Total TCH)x 100 LOADfactor
t <= 3 - 16 dB t <= 10% +10 dB
3 < t <= 8 - 8 dB 10% < t <= 25% +5 dB
8 < t <= 15 0 dB 25% < t <= 50% 0 dB
15 < t <= 21 +7 dB 50% < t <= 80% -10 dB
21 < t +10 dB 80% < t -15 dB
1.321
1.322
1.323
1.324
Back
Cause 12
Back
Cause 26
1.325
1.326
1.327
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Erlang B law
Frequency hopping influence on PCHO process
Load & Traffic evaluation
Training exercises solutions
Handover Protocol
1.328
BTS BSC
HO Preparation
Radio Active
Link HO Candidate
Channel HO Detection
Measurements Cell Evaluation
Pre-processing
HO
management
HO
protocol
MSC
1.329
REJ_CELL_LIST
cells internally rejected by the MSC or BSC
MS_CELL_REJ_LIST
cells to which the MS failed to hand over
1.330
Since B6 release, some changes have been provided to the HO management process which is in charge of the HO
execution triggering, when the need of handover is detected by the HO preparation process.
These changes are :
use of the T_FILTER parameter in a different way than for B5,
the parameter NBR_HO_ATTEMPTS which was used for internal HO in B5 is removed,
use of the T7 parameter and of the REJ_CELL_LIST list also for internal HO in B7,
same behavior in case of internal and external HO in B7,
immediate attempt after rejection or failure without waiting for a new alarm in case of internal and external HO
in B7,
implicit rejection of cells in B7 with the help of the target cell identity in the HO command received from the
MSC.
If the candidate cell list provided by the candidate cell evaluation process is different from the previous one (the number
of cells is different or same number of cells but new cells in the list), an alarm is sent to the HOM process. In B7, if
T_FILTER expires, it means that the HO is no more necessary.
For both internal and external HOs in case of HO failure from the MS, the cell is filtered until the expiry of the
T_MS_CELL_REJ timer. When the T_MS_CELL_REJ timer expires, the rejected cell may be a candidate.
In B7 release, T7 timer is used to manage the REJ_CELL_LIST list and a subsequent HO REQUIRED can be sent to
the MSC before T7 expiry if the target cell list has changed (new cell or removed cell).
The REJ_CELL_LIST list is used for both internal and external Hos.
T_HO_REQD_LOST Expiry
This timer is used to supervise response from the MSC. It is started when sending the first HANDOVER
REQUIRED to the MSC and it is stopped in the following cases:
when HANDOVER COMMAND is received from the MSC or
when HANDOVER REQUIRED REJECT is received from the MSC only if the same number of
HANDOVER REQUIRED REJECT messages have been received from the MSC than the number of HANDOVER
REQUIRED messages sent to the MSC for this channel change procedure) (i.e. no message crossing over A
interface).
In case where more HANDOVER REQUIRED messages have been sent to the MSC, the timer
T_HO_REQD_LOST is not stopped upon HANDOVER REQUIRED REJECT receipt, as there is no way for the
BSC to know if the received HANDOVER REQUIRED REJECT is a response to the last HANDOVER
REQUIRED message or a response to a previous one (message crossing over A interface).
On expiry, an O&M error report is raised only when no message has been received from the MSC since the last
HANDOVER REQUIRED message, and the external channel change procedure is terminated.
1.332
HO mgt HO prot
ordered filtered
1. Cell1 Cell1 HO to
2. Cell2 - Cell2 cell3
3. Cell3 Rej. lists 1. Cell3
MS BSC/MSC
cell2 cell1
1.333
1.334
No handover is on-going
A handover is on-going
Yes Is No
T_FILTER
running ?
Start T_FILTER
Yes No An HO alarm containingthe candidatecell
Isthe candidatecell
list issent to the HO management
entity
list different from
thepreviousone ?
Restart T_FILTER
Restart T_FILTER
An HOalarm containingthe candidatecell
list issent to the HO management
entity
T_FILTER is restarted
each time the alarm is Back
still on
1.335
1.336
Alcatel University - 8AS 90200 1485VH ZZA Ed.02
Erlang B law
Frequency hopping influence on PCHO process
Load & Traffic evaluation
Training exercises solutions
A: ARC_SIZE_FACTOR
r2 B: MIN_RADIUS_FACTOR
C: MAX_RADIUS_FACTOR Back
1.337
An ellipsoid arc is a shape characterised by the co-ordinates of an ellipsoid point o (the origin), inner radius r1,
uncertainty radius r2, both radii being geodesic distances over the surface of the ellipsoid, the offset angle () between
the first defining radius of the ellipsoid arc and North, and the included angle () being the angle between the first and
second defining radii. The offset angle is within the range of 0 to 359,999 while the included angle is within the
range from 0,0001 to 360. This is to be able to describe a full circle, 0 to 360
For CI+TA method which is default one , the answer is given by description of "ellipsoid arc".
Optimization parameters:
ARC_SIZE_FACTOR
Factor used in the computation of the width in degree of the ellipsoid arc returned by the MFS when
computing location estimate based on TA positioning method.
MIN_RADIUS_FACTOR
Factor used in the computation of the minimum radius of the ellipsoid arc returned by the MFS when
computing location estimate based on TA positioning method
MAX_RADIUS_FACTOR
Factor used in the computation of the maximum radius of the ellipsoid arc returned by the MFS when
computing location estimate based on TA positioning method