RNO Analysis Mate V1 01

RNO Analysis Mate
Developed By: Manik Kapoor

Contact: Maanikkapoor@Outlook.Com
RNO Mate
1 3G Congestion HW
2 Channel Element
3 3G Events
4 CQI
5 Cpich Power
6 F1 F2 Layering Policy
7 GSM DCS Traffic Sharing
8 Handover 2G
9 2G Cell Reselection
10 Frequency Hopping Parameters
11 2G Congestion
12 2G Handover Problem
13 2G Call Drop
14 2G Power Control
15 2G DCR HW Parameter
16 Counter Relationship HW
17 3G Congestion NSN
18 Congestion Huawei 2G
19 Congestion Nokia 2G
20 Congestion Siemens 2G
21 Events Preventive
22 3G Huawei RTWP
23 3G Huawei-HSDPA & HSUPA
Mate
Click to return to main page
Case 1st Action
Verify CE license and CE board capability.
CE Blocking/CE High Util Commands involved : DSP LICENSE, DSP
BBPTC
Iub Blocking/Iub High Util Verify Iub BW setting in Node-B and in

RNC. Sets involved : IPPATH, IPLOGICPORT
DL- Power Blocking/DL - Power High Util Physical Audit
UL- Power Blocking Physical Audit
Code Blocking Physical Audit

2nd Action 3rd Action
Physical Audit CE license and/or board upgrade
Physical Audit Iub BW upgrade
Modify DL CAC parameters set to

higher value. Parameters involved :
Activate 40W, maintain existing PCPICH DLCONVAMRTHD,
setting DLCONVNONAMRTHD,
DLOTHERTHD, DLHOTHD,
DLCELLTOTALTHD
Increase ULTOTALEQUSERNUM (e.g Turn-off

NBMULCACALGOSELSWITCH (set to
from 160 to 180) ALGORITHM_OFF)
Modify DLHOCECODERESVSF to lower Reduce HSPDSCHMINCODENUM
SF (e.g from SF32 to SF 64) (e.g from 5 to 4)
4th Action
Modify LDR threshold. Sets involved :

UCELLLDM, UCELLLDR
Modify FTI to reduce Active Factor. Sets

involved : TRMFACTOR, ADJMAP,
ADJNODE
Reduce HSSCCHCODENUM (e.g from 4

to 3)
Channel Element (CE) Resource
CE resources are a type of NodeB hardware resource. The number of CEs supported by single NodeB indicates the channel demodula
NodeB. The more CEs a NodeB supports, the more powerful the channel demodulation and service processing capabilities for serving the
rates require different numbers of CEs to ensure proper channel demodulation.
In a RAN, CE resources are managed by both the RNC and NodeB. The NodeB reports its CE capacity to the RNC. The RNC determines
based on the number of CEs that need to be consumed and controls CE resources during CE congestion. This ensures the proper u
dynamically manages CE resources and rapidly adjusts the number of CEs that can be consumed based on the actual service rate. This incre
A proper use of CE resources increases the number of UEs that can be admitted and improves the service quality of the admitted UEs.
Basic Channel Element Concepts

CE is a basic unit that measures the channel demodulation capabilities of a NodeB. CEs are classified into uplink (UL) CEs and downlink (DL)
One UL CE needs to be consumed by a UL 12.2 kbit/s voice service (SF = 64) plus 3.4 kbit/s signaling.
One DL CE needs to be consumed by a DL 12.2 kbit/s voice service (SF = 128) plus 3.4 kbit/s signaling.
If only 3.4 kbit/s signaling traffic is carried on a DCH or HSPA channel, one CE still needs to be consumed. The number of CEs that need
other types can be calculated by analogy.
The number of UL and DL CEs supported by a NodeB is determined by the NodeB hardware capabilities and the licensed CE capacity.
supported by the NodeB hardware is called the physical CE capacity. The licensed CE capacity may differ from the physical CE capacity. The
of CEs that can be used by an operator.
CE is a concept of the NodeB side. On the RNC side, it is called NodeB credit. The RNC performs admission and congestion control based
the number of Node credit resources is twice that of CEs. In the DL, the number of NodeB credit resources equals that of CEs.
CE Sharing in a Resource Group

To facilitate baseband resource management, NodeB baseband resources fall into UL and DL resource groups. The UL and DL resource gro
other.
UL Resource Group
UL resource group is a UL resource pool shared on a per-channel basis, more than one cell can be setup in one UL resource group, O
multiple baseband boards, but one board can belong to only one UL resource group. CE resources in one UL resource group can be sh
means that UEs in a cell in a UL resource group can set up services on any board in the group. The physical CE capacity of a UL resource
baseband boards in the group.
DL Resource Group
Different from a UL resource group, a DL resource group is shared on a per-cell basis. Resources in a DL resource group are allocated to
cells; one board can be configured to multiple DL resource groups. DL CE resources for UEs in the same cell can be provided by any bas
group. CE resources in one DL resource group can be shared only within a baseband board.
NodeB CE Capacity Specifications

Typically different baseband boards of a NodeB have their own CE capacity specifications. For exampled, the detailed CE capacity specifica
baseband board, see the BBU3900 Hardware Description product by Huawei
CE capacity here refers to the number of CEs that can be consumed by UL and DL R99 services and HSUPA services. It does not include CE r
for common and HSDPA channels.
Rules for Calculating CE Consumption

The RNC determines the number of CEs required for a service based on the SF that matches the service rate. When an RAB connection is
CE resources must be allocated or taken back and the number of CEs must be deducted or added accordingly. Different rules for calculating
to channels or services of different types.
CE resources reserved by the NodeB for common and HSDPA channels are shown in gray.
CE resources that need to be consumed by R99 and HSUPA services are shown in pink.
Common Channels CE Consumption

CE resources required on the UL and DL common channels are reserved by the NodeB. Therefore, they do not occupy the licensed CE cap
be considered in the calculation of CE consumption.
HSDPA Channels CE Consumption

Similarly, the NodeB reserves CE resources for the high-speed downlink shared channel (HS-DSCH) and the related control channels if HSDP
need to be considered in the calculation of CE consumption.
Note that the signaling of an HSDPA UE that is not performing an R99 service occupies one DCH and needs to consume one DL CE. If
enabled, the signaling of an HSDPA service does not consume additional CE resources. For an HSDPA UE that is performing an R99 service,
occupy the same DCH. Therefore, only the CEs consumed on R99 traffic channels need to be calculated.
R99 Service CE Consumption

For an R99 service, the RNC determines the number of CEs and NodeB credit resources that need to be consumed based on the SF that ma
(MBR) of the service.
Direction
UL
DL
HSUPA Service CE Consumption

For an HSUPA service, the RNC determines the number of CEs and NodeB credit resources that need to be consumed based on the SF th
RNC determines the SF based on a certain rate in the following ways:
If the UL enhanced L2 function is disabled and the NodeB indicates in a private information element (IE) that dynamic CE resource manag
cell, the RNC calculates the SF based on the larger of the bit rate of one RLC PDU and the guaranteed bit rate (GBR).
If the UL enhanced L2 function is disabled, the RLC PDU size is fixed. The bit rate of one RLC PDU is determined by the RLC PDU size and tra
If the UL enhanced L2 function is enabled and the NodeB indicates in a private IE that dynamic CE resource management has been enable
the SF based on the larger of the bit rate of the smallest RLC PDU and the GBR.
If the UL enhanced L2 function is enabled, the RLC PDU size is flexible. The bit rate of the smallest RLC PDU is determined by the minimu
minimum RLC PDU size can be specified by the RlcPduMaxSizeForUlL2Enhance parameter.
If the NodeB reports that dynamic CE resource management has been disabled, the RNC calculates the SF based on the MBR.
If the NodeB does not report whether dynamic CE resource management has been enabled, the RNC calculates the SF
HsupaCeConsumeSelection parameter and whether the UL enhanced L2 function is enabled.
If HsupaCeConsumeSelection is set to MBR, the RNC calculates the SF based on the MBR.
If HsupaCeConsumeSelection is set to GBR:
If the UL enhanced L2 function is disabled, the RNC calculates the SF based on the larger of the bit rate of one RLC PDU and the GBR.
If the UL enhanced L2 function is enabled, the RNC calculates the SF based on the larger of the bit rate of the smallest RLC PDU and the GB
After determining the SF, the RNC searches the CE consumption mapping listed below
Direction
UL
CE Consumption of 4-Way Receive Diversity

The use of 4-way receive diversity does not affect DL CE consumption but doubles UL CE consumption. The use of 4-way receive diversit
group. UL CE consumption of a resource group doubles if the resource group is configured with 4-way receive diversity. CE consumptio
remains unchanged.
examples of CE Consumption
UE A, which performs a UL 64 kbit/s and DL 384 kbit/s service on the DCH, consumes three UL CEs and eight DL CEs.
UE B, which performs a UL 64 kbit/s and DL 1024 kbit/s service on the DCH and HS-DSCH respectively, consumes three UL CEs and one
bearer (SRB) is carried on the DCH.
UE C, which performs a UL 608 kbit/s and DL 1024 kbit/s service on the E-DCH and HS-DSCH respectively and at the same time performs an
nine UL CEs and one DL CE.
Rate (kbit/s) SF Number of CEs Corresponding
Consumed Credits Consumed
3.4 256 1 2
13.6 64 1 2
8 64 1 2
16 64 1 2
32 32 1.5 3
64 16 3 6
128 8 5 10
144 8 5 10
256 4 10 20
384 4 10 20
3.4 256 1 1
13.6 128 1 1
8 128 1 1
16 128 1 1
32 64 1 1
64 32 2 2
128 16 4 4
144 16 4 4
256 8 8 8
384 8 8 8
Rate (kbit/s) SF Number of CEs Corresponding
Consumed Credits Consumed
8 64 1 2
16 64 1 2
32 32 1 2
64 32 1 2
128 16 2 4
144 16 2 4
256 8 4 8
384 4 8 16
608 4 8 16
1450 2SF4 16 32
2048 2SF2 32 64
2890 2SF2 32 64
5760 2SF2+2 48 96
SF4
Event Name
event 1A
event 1B
event 1C
event 1D
event 1E
event 1F
event 1G
event 1H
event 1I
Event 2a
Event 2b
Event 2c
Event 2d
Event 2e
Event 2f
Event 3a
Event 3b
Event 3c
Event 3d
event 4 A
event 4 B
event 5A
event 6A
event 6B
event 6C
event 6D
event 6E
event 6F
event 6G
Event 7a
Event 7b
Event 7c
Desription
A Primary CPICH enters the reporting range; addition of a radio link.
A primary CPICH leaves the reporting range; removal of a radio link.
A non-active primary CPICH becomes better than an active primary CPICH; replacement of the worst cell in AS.
Change of best cell
A Primary CPICH becomes better than an absolute threshold
A Primary CPICH becomes worse than an absolute threshold
Change of best cell (TDD)
Timeslot ISCP below a certain threshold (TDD)
Timeslot ISCP above a certain threshold (TDD)
Change of best frequency

The estimated quality of the currently used frequency is below a certain threshold and the estimated quality of a non-used fre
The estimated quality of a non-used frequency is above a certain threshold
The estimated quality of the currently used frequency is below a certain threshold; start compressed mode to measure inter-f
The estimated quality of a non-used frequency is below a certain threshold
The estimated quality of the currently used frequency is above a certain threshold; stop compressed mode & stop measure int
The estimated quality of the currently used UTRAN frequency is below a certain threshold and the estimated quality of the oth
The estimated quality of other system is below a certain threshold
The estimated quality of other system is above a certain threshold
Change of best cell in other system
Transport Channel Traffic Volume becomes larger than an absolute threshold

Transport Channel Traffic Volume becomes smaller than an absolute threshold
A predefined number of bad CRCs is exceeded
The UE Tx power becomes larger than an absolute threshold; start compressed mode
The UE Tx power becomes less than an absolute threshold; stop compressed mode
The UE Tx power reaches its minimum value
The UE Tx power reaches its maximum value
The UE RSSI reaches the UE's dynamic receiver range
The UE Rx-Tx time difference for a RL included in the active set becomes larger than an absolute threshold
The UE Rx-Tx time difference for a RL included in the active set becomes less than an absolute threshold
The UE position changes more than an absolute threshold

SFN-SFN measurement changes more than an absolute threshold
GPS time and SFN time have drifted apart more than an absolute threshold
CQI stands for Channel Quality Indicator. As the name implies, it is an indicator carrying the information on how good/bad the commun
This CQI is for HSDPA.
CQI is the information that UE sends to the network and practically it implies the following two
i) Current Communication Channel Quality is this-and-that..
ii) I (UE) wants to get the data with this-and-that transport block size, which in turn can be directly converted into throughput
In HSDPA, the CQI value ranges from 0 ~ 30. 30 indicates the best channel quality and 0,1 indicates the poorest channel quality. Depending
network transmit data with different transport block size. If network gets high CQI value from UE, it transmit the data with larger transport
What if network sends a large transport block even though UE reports low CQI, it is highly probable that UE failed to decode it (cause CRC e
send NACK to network and the network have to retransmit it which in turn cause waste of radio resources.
What if UE report high CQI even when the real channel quality is poor ? In this case, network would send a large transport block size accord
would become highly probable that UE failed to decode it (cause CRC error on UE side) and UE send NACK to network and the network hav
turn cause waste of radio resources.
How UE can measure CQI ? This is the most unclear topic to me. As far as I know, there is no explicit description in any standard on the m
CQI is calculated, but it is pretty obvious that the following factors play important roles to CQI measurement.
signal-to-noise ratio (SNR)

signal-to-interference plus noise ratio (SINR)
signal-to-noise plus distortion ratio (SNDR)
It is not defined in the specification on how these factors are used and whether there is any other factors being involved. The implementati
makers. Usually at chipset development stage, they do a lot of testing to correlate the measured SNR and the measured BLER by the chipse
table (or equation) for the correlation. And the mapping table (function) would eventually used to determine CQI value.
In LTE, there are 15 different CQI values randing from 1 to 15 and mapping between CQI and modulcation scheme, transport block size is
(36.213)
If you are an engineer in Network (eNodeB) programming, you need to know the number of resource blocks and MCS for each CQI value to
CQI
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Note 1 : Refer to Throughtput Calculation Example for determining N_RB, MCS, TBS determination.
Note 2 : REs/PRB varies depending on CFI value as follows.
CFI
1
2
3
Note 3 : I used the following formula explained in Code Rate section.

v_CodingRate := (int2float(p_TBSize + 24)) / (int2float(p_N_PRB * tsc_REs_Per_PRB * v_BitsPerSymbol));
CQI is carried by PUCCH or PUSCH depending on the situation as follows.
Carried by PUCCH : Periodic CQI

Carried by PUSCH : Aperiodic CQI.
Regarding CQI report period and configuration, refer to CQI, PMI, RI Reporting Configuration part.
< Two Important CQI Table >
We have two different tables as shown below defined in 36.213. Now the question is in which situation the first table (Table 7.2.3-1) is used
second table(Table 7.2-1) is used). Overall story is described in 36.213 section 7.2, I will just re-organize those statements in a little bit diffe
The table shown above is used in following situation. In this table, 4 bit is used to indicate each CQI value.
1) For transmission modes 1, 2, 3 and 5, as well as transmission modes 8, 9 and 10 without PMI/RI reporting, transmission mode 4 with
modes 8, 9 and 10 with PMI/RI reporting and RI=1
2) For RI > 1 with transmission mode 4, as well as transmission modes 8, 9 and 10 with PMI/RI reporting, PUSCH based triggered reporti
the 4 bit CQI (16 different value) is reported for each Codeword (CW0 and CW1).
Following is another table that is used for CQI report, but this is not the absolute value. It is a different value for two different CQI value. Th
defined ? It is defined as follows :
Codeword 1 offset level = wideband CQI index for codeword 0 wideband CQI index for codeword 1.
This table is used in following case :
1) For RI > 1 with transmission mode 4, as well as transmission modes 8, 9 and 10 with PMI/RI reporting, PUCCH based reporting includ
wideband CQI for codeword 0 according to Table 7.2.3-1 and a wideband spatial differential CQI
Modulation Bits/Symbol REs/PRB N_RB MCS TBS Code Rate
QPSK 2 138 20 0 536 0.101449
QPSK 2 138 20 0 536 0.101449
QPSK 2 138 20 2 872 0.162319
QPSK 2 138 20 5 1736 0.318841
QPSK 2 138 20 7 2417 0.44221
QPSK 2 138 20 9 3112 0.568116
16QAM 4 138 20 12 4008 0.365217
16QAM 4 138 20 14 5160 0.469565
16QAM 4 138 20 16 6200 0.563768
64QAM 6 138 20 20 7992 0.484058
64QAM 6 138 20 23 9912 0.6
64QAM 6 138 20 25 11448 0.692754
64QAM 6 138 20 27 12576 0.76087
64QAM 6 138 20 28 14688 0.888406
64QAM 6 138 20 28 14688 0.888406
REs/PRB
150
138
126
CPICH power typically takes about 8~10% of the total NodeB power. For a 20W (43dBm) NodeB
(35.1 ~ 33dBm).
In urban areas where in-building coverage is taken care of by in-building installations, the CPICH may sometimes go as low as 5
1) The coverage area is small since users are close to the site, and
2) More power can be allocated to traffic channels
For traffic balancing using HODCS - DCS / GSM - GSM : means same layer, you can using PBGT HO parameterDCS - GSM / GSM - DCS : means different layer,
your reference)or you may set CRO for DCS bigger than GSM to attract more traffic to DCS and reduce ping-pong HO,or you can enable LOADHOEN paramet
attachment. _____________ The same layer of Cell, you can optimize with PBGT HO Threshold, CRO or load handover support parameters but difference la
Inter-Layer HO Threshold:30
Inter-Layer HO Hysteresis:31
EDGE DL HO Threshold:25
When G18 stand for Serving Cell-RxLev of GSM1800 lower than-83dBm will HO to GSM900 trigger by EDGE HO=-85dBm2- When G18 satnd for Neighbor-R
Layer HO . Depending on your settings, retuning some parameters among the below listed mayhelp you achieve the desired Traffic Balance;
Inter-layer HO ThresholdREXLEV_ACCESS_MINTch Traffic busy Threshold(%)AMR TCH/H Prior Cell Load ThresholdEdge HO UL RX_LEV ThresholdEdge HO DL
UL RX_LEV Upper ThresholdAMR UL RX_LEV Lower ThresholdDL RX_LEV Upper ThresholdDL RX_LEV Lower ThresholdUL RX_LEV Upper ThresholdUL RX_LE
CRO
Load HO Allowed
Load HO Threshold
REXLEV_ACCESS_MIN
Tch Traffic busy Threshold(%)
AMR TCH/H Prior Cell Load Threshold
Edge HO UL RX_LEV Threshold
Edge HO DL RX_LEV Threshold
AMR DL RX_LEV Upper Threshold
AMR DL RX_LEV Lower Threshold
AMR UL RX_LEV Upper Threshold
AMR UL RX_LEV Lower Threshold
DL RX_LEV Upper Threshold
DL RX_LEV Lower Threshold
UL RX_LEV Upper Threshold
UL RX_LEV Lower Threshold
UL Expected Level at HO Access
Handover and Related Parameters

4.8.1PBGT Handover Threshold (HoMargin)
I.Definition
The PBGT handover threshold is power handover tolerance (handover in serving areas). When the sign
higher than that of the serving cell, handover occurs. Complex radio propagation conditions cause flu
tolerance avoids frequent handover at bordering areas. The PBGT handover threshold is similar to HO
II.Format
The PBGT handover threshold ranges from 0 to 127, corresponding to 64 dB to +63 dB. The reference
reference value for urban areas is 70 to 72.
III.Configuration and Influence
The PBGT handover threshold aims to adjust handover difficulty properly, and to avoid ping-pong han
handover is delayed and handover is less efficient. When it is smaller than 64, the MS hands over from
with lower level.
4.8.2Minimum Downlink Power of Handover Candidate Cells (rxLevMinCell)
I.Definition
It is the minimum allowed access level for a cell to be a neighbor cell. When the cell level measured
BSS list the cell into candidate cell list for handover judgment.
II.Format
It ranges from 110 dBm to 47 dBm.
It is helpful in the following two aspects:
lIt guarantees communication quality.
For a common single layer network structure, the value ranges from 90 dBm to 80 dBm.
lIt helps allocate traffic between cells averagely.
Especially in multi-layer network structure, to maintain MS in a network layer, you can incre
layer (such as 70 dBm), and also decrease that in other cells.
IV.Precautions
You cannot configure rxLevMinCell over great (over 65 dBm) or over small (lower than 95 dBm), and
affected.
4.8.3Handover Threshold at Uplink Edge
I.Definition
If the uplink received level keeps being smaller than the handover threshold at uplink edge for a peri
II.Format
It ranges from 0 to 63, corresponding to 110 dBm to 47 dBm. The recommended values are as follow
lConfigure it to 25 in urban areas without PBGT handover.
lConfigure it to 20 in single site of suburban areas.
lConfigure it to 20 in urban areas with PBGT handover
When PBGT handover is enabled, the corresponding edge handover threshold can be lowered. When P
handover threshold is over low, an artificial cross-cell non-handover occurs. Therefore call drop occu
interference occur due to cross-cell talk.
4.8.4Handover Threshold at Downlink Edge
I.Definition
If the downlink received level keeps being smaller than the handover threshold at downlink edge for
performed.
II.Format
It ranges from 0 to 63, corresponding to 110 dBm to 47 dBm. The recommended values are as follow
lConfigure it to 30 in urban areas without PBGT handover.
lConfigure it to 25 in single site of suburban areas.
lConfigure it to 25 in urban areas with PBGT handover
When PBGT handover is enabled, the corresponding edge handover threshold can be lowered. When P
handover threshold is over low, an artificial cross-cell non-handover occurs. Therefore call drop occu
interference occur due to cross-cell talk.
4.8.5Downlink Quality Restriction of Emergency Handover
I.Definition
If the downlink received quality is lower than the threshold of downlink quality restriction of emerge
emergency handover occurs.
II.Format
It ranges from 0 to 70, corresponding to RQ (QoS 0 to 7) x 10.
The recommended value is 50.
When frequency hopping is enabled, the voice quality is better with the same RQ, you can configure
occurs, the intracell handover occurs first. If there are no other candidate cells, and the intracell ha
occurs.
4.8.6Uplink Quality Restriction of Emergency Handover
I.Definition
If the uplink received quality is lower than it, quality difference emergency handover is triggered.
II.Format
occurs, the intracell handover occurs first. If there are no other candidate cells, and the intracell ha
occurs.
4.8.7Uplink Quality Threshold of Interference Handover
I.Definition
It is the uplink received quality threshold of the serving cell that triggers interference handover. The
the following conditions are met:
lThe uplink received level is higher than the uplink received power threshold of interfer
lThe uplink received quality is lower than the uplink quality threshold of interference h
When handover switch is enabled, the interference handover occurs within the cell by preference.
II.Format
handover is triggered, select the candidates according to the sorted result. If the serving cell ranks fi
the MS selects the serving cell; otherwise it selects the second candidate cell.
4.8.8Downlink Quality Threshold of Interference Handover
I.Definition
It is the downlink received quality threshold of the serving cell that triggers interference handover. T
all the following conditions are met:
lThe downlink received level is higher than the downlink received power threshold of in
lThe downlink received quality is lower than the downlink quality threshold of interfere
II.Format
handover is triggered, select the candidates according to the sorted result. If the serving cell ranks fi
the MS selects the serving cell; otherwise it selects the second candidate cell.
IV.Precautions
The interference handover quality must be better than emergency handover quality.
4.8.9Uplink Received Power Threshold of Interference Handover
I.Definition
If interference handover occurs due to uplink quality, the serving cell must reach the minimum uplin
the system judges that uplink is interfered, so interference handover is triggered.
The interference handover is triggered if all the following conditions are met:
lThe uplink received level is higher than the uplink received power threshold of interfer
lThe uplink received quality is lower than the uplink quality threshold of interference h
II.Format
It ranges from 0 to 63, corresponding to 110 dBm to 47 dBm.
III.Configurationa and Influence
When interference handover is triggered, select the candidates according to the sorted result. If the
handover is enabled, the MS selects the serving cell; otherwise it selects the second candidate cell.
4.8.10Downlink Received Power Threshold of Interference Handover
I.Definition
If interference handover occurs due to uplink quality, the serving cell must reach the minimum down
met, the system judges that downlink is interfered, so interference handover is triggered.
The interference handover is triggered if all the following conditions are met:
lThe downlink received level is higher than the downlink received power threshold of in
lThe downlink received quality is lower than the downlink quality threshold of interfere
II.Format
It ranges from 0 to 63, corresponding to 110 dBm to 47 dBm.
When interference handover is triggered, select the candidates according to the sorted result. If the
handover is enabled, the MS selects the serving cell; otherwise it selects the second candidate cell.
4.8.11Maximum Repeated Times of Physical Messages (NY1)
I.Definition
In asynchronous handover process of GSM system, when the MS receives handover messages of the ne
on the target channel. After the network receives the message, it does as follows:
1)Calculate related RF features.
2)Send physical messages (it the channel messages are encrypted, start encryption and d
3)Start timer T3105.
If the network does not receive correct layer 2 frames sent by MS until expiration of T3105, the netw
restart T3105. The maximum times for resending physical messages is determined by the parameter m
messages (NY1)
II.Format
NY1 ranges from 0 to 254.
When the network receives the handover access messages sent by MS, the physical channel (PCH) nee
communication quality on channels is guaranteed, the MS can receive physical messages correctly an
If the physical messages are sent multiple times, and the network cannot receive layer 2 frames sent
communicate normally. Though link is setup after multiple trials, the communication quality is not gu
radio resources. Therefore configure NY1 to a smaller value.
IV.Precautions
Configuring NY1 is affected by T3105. If T3105 is configured to a short value, then the NY1 needs to b
If a handover trial fails before the original cell receives the HANDOVER FAILURE message, and the T3
times, the target BTS sends a CONNECTION FAILURE INDICATION message to the target BSC. Though t
channel, the traffic measurement counters from multiple vendors will take statistics of connection fa
To avoid the previous phenomenon, configure T3105 as follows:
Ny * T3105 > T3124 + delta (delta: the time between expiration of T3124 and receiving HANDOVER FA
4.8.12Multiband Indicator (multiband_reporting)
I.Definition
In a single band GSM network, when the MS send measurement reports of neighbor cells to the netwo
six neighbor cells with strongest signals.
In a multiband network, operators wish that MS uses a band by preference in cross-cell handover. The
reports according to signal strength and signal band. The parameter multiband indicator indicates MS
cells.
II.Format
The multiband indicator ranges from 0 to 3, with meanings as follows:
l0:
According to signal strength of neighbor cells, the MS must report six allowed measu
strongest signals and known NCC, with the neighbor cells in whatever band.
l1:
The MS must report the allowed measurement report of a neighbor cell with known
band expect for the band used by the serving cell. The MS must also report the neighbor cell
rest locations. If there are other rest locations, the MS must report conditions of other neigh
l2:
The MS must report the allowed measurement report of two neighbor cells with know
band expect for the band used by the serving cell. The MS must also report the neighbor cell
rest locations. If there are other rest locations, the MS must report conditions of other neigh
MS must report the allowed measurement report of three neighbor cells with kn
l3:The
each band expect for the band used by the serving cell. The MS must also report the neighbo
cell in rest locations. If there are other rest locations, the MS must report conditions of othe
In multiband networks, it is related to traffic of each band. For configuration, refer to the following
lIf
the traffic of each band is approximately equal, and operators do not select a band i
multiband indicator to 0
lIf
the traffic of each band is obviously different, and operators want MS to select a ban
multiband indicator to 3.
lFor situations between the previous two, configure multiband indicator to 1 or 2.
4.8.13Permitted Network Color Code (ncc permitted)
I.Definition
During a talk, the MS must report the measured signals of neighbor cells to the base station, but each
Therefore the MS is configured to report the potential handover target neighbor cells, instead of repo
signal level.
To enable previous functions, restrict MS to measure the cells with the fixed network color code (NCC
the NCCs of the cells to be measured by MS. The MS compares the measured NCC of neighbor cells an
measured NCC is in the set, the MS reports the NCC to the base station; otherwise, the MS discard the
II.Format
The parameter ncc permitted is a bit mapping value, consisting of 8 bits. The most significant bit is b
Each bit corresponds to an NCC code 0 to 7 (see GSM regulations 03.03 and 04.08).
If the bit N is 0 (N ranges from 0 to 7), the MS needs not to measure the level of the cell with NCC of
quality and level of the cells corresponding to bit number of 1 in NCC and ncc permitted configuratio
Each area is allocated with one or more NCCs. In the parameter ncc permitted of the cell, the local N
excluded, abnormal handover and call drop occur. For normal roaming between areas, the NCC of ne
cells of an area.
IV.Precautions
Improper configuration of the parameter causes normal handover and even call drop. The parameter
Serial Parameters of Cell Selection and Reselection

4.3.1cell_bar_access
I.Definition
In the SI broadcasted in each cell, a bit indicates whether the MS is allowed to access the network in
II.Format
The value of cell_bar_access includes 1 and 0. The value 0 indicates that MS is allowed to access the
the MS is barred to access the network from the cell. Actually whether to allow MS to access the netw
cell_bar_access and cell_bar_qualify.
The cell_bar_access is configured by equipment room operators. Usually the MS is allowed to access t
configured to 0. In special situations, the operators want some cell for handover service only, so cell_
The MS usually works in microcells (you can configure the priority of cells and reselection parameters
moving fast, the network force MS to hand over to the base station G. The signals of base station G a
areas. When the call terminates, the MS just camps near base station G and at edge of microcell cell
regulations, therefore the MS cannot return to microcell.
The capacity of base station G is usually small, so the previous phenomenon leads to congestion of ba
configure the cell_bar_access to 1, namely, to forbid MS directly accessing base station G. In area A,
IV.Precautions
The cell_bar_access is used only in some special areas. For common cells, it is configured to 0.
4.3.2cell_bar_qualify
I.Definition
The cell_bar_qualify determines the priority of cells, namely, it enables MS to select some cell by pre
II.Format
The value of cell_bar_qualify includes 1 and 0. The cell_bar_qualify and cell_bar_access determine t
Table 7-1 Cell priorities
cell_bar_qualify
An exception is that the cell selection priority and cell reselection state are normal when the followi
lThe cell belongs to the PLMN which the MS belongs to.
lThe MS is in cell test operation mode.
lThe cell_bar_access is 1.
lThe cell_bar_qualify is 0.
lThe access control class 15 is disabled.
The priority of all the cells are usually configured tonormal, namely, cell_bar_qualify = 0. In microc
MS to camps on the cell of some type by preference. In this situation, the equipment room operators
tonormaland other cells tolow.
During cell selection, when the proper cells with normal as the priority is not present (proper cells m
cell selection, namely, C1 > 0, and the cell is allowed to access), the MS will select cells with low pri
IV.Precautions
Pay attention to the following aspects:
lWhen
cell priority is used as a method to optimize network, the cell_bar_qualify only a
reselection. You must optimize the network by combining cell_bar_qualify and C2.
lDuring
cell selection, when the proper cells with normal as the priority is not present,
when the level of the cell with normal priority is low, and cells with low priority and high le
slowly while powering on.
4.3.3Minimum Received Level Allowing MS to Access (RXLEV_ACCESS_MIN)
I.Definition
To avoid bad communication quality, call drop, and a waste of network radio resources due to MS acc
GSM regulations prescribe that when an MS accesses the network the received level must be greater
received level allowing MS to access.
II.Format
The value range of RXLEV_ACCESS_MIN is from 110 dBm to 47 dBm.
The recommended RXLEV_ACCESS_MIN needs to be approximately equal to the receiving sensitivity o
parameter C1, so it is important to traffic adjustment and network optimization.
For cells with over high traffic and severe congestion, you can increase RXLEV_ACCESS_MIN. In this w
effective coverage range decreases. You must not configure RXLEV_ACCESS_MIN over great, because
complaints for signal fluctuation. It is recommended that the RXLEV_ACCESS_MIN is smaller than or e
IV.Precautions
Except for areas of high density of base stations and of qualified coverage, adjusting cell traffic by R
4.3.4Additional Reselection Parameter Indicator
I.Definition
The cell selection and reselection by MS depends on the parameters C1 and C2. Whether C2 is the ce
operators. Additional reselection parameter indicator (ADDITIONAL RESELECT) informs MS of whether
II.Format
ADDITIONAL RESELECT consists of 1 bit. In SI3, it is meaningless, and equipment manufacturers config
SI4.
lWhen
ADDITIONAL RESELECT is configured to N, the meaning is: if the rest bytes of SI4
and calculate parameters related to C2 and related cell reselection parameter PI.
lWhen
ADDITIONAL RESELECT is configured to Y, the meaning is that the MS must abstra
related cell reselection parameter PI.
Cells seldom use SI7 and SI8, so you can configure ADDITIONAL RESELECT to N. When cells use SI7 and
reselection, you can configure ADDITIONAL RESELECT to Y.
4.3.5Cell Reselection Parameter Indicator
I.Definition
The cell reselection parameter indicator (CELL_RESELECT_PARAM_IND) is used in informing MS of whe
whether C2 is present.
II.Format
The value of CELL_RESELECT_PARAM_IND includes Y and N, with the meanings as follows:
lY: The MS must calculate C2 by abstracting parameters from SIs of cell broadcast, and
lN: The MS must set C1 as the standard, namely, C2 = C1.
The equipment room operators determine the value of PI. Configure PI to Y if related cells set C2 as
configure it to N.
4.3.6Cell Reselection Offset, Temporary Offset, and Penalty Time
I.Definition
After the MS selects a cell, without great change of all the conditions, the MS will camp on the select
lStarts measuring signals level of BCCH carrier in neighbor cells.
lRecords the 6 neighbor cells with greatest signal level.
lAbstract various SI and control information of each neighbor cell from the 6 cells.
When conditions are met, the MS hands over from the selected cell to another. This process is called
lCell priority
lWhether the cell is barred to access
lRadio channel level (important)
When the signal level of neighbor cells exceeds that of the serving cell, cell reselection occurs. The c
C2, with the calculation as follows:
1)When PENELTY_TIME 11111:
C2 = C1 + CELL_RESELECT_OFFSET - TEMPORARY_OFFSET * H (PENALTY_TIME - T)
Wherein, if PENALTY_TIME - T (x) < 0, the function H(x) = 0; if x 0, H(x) = 1.
2)When PENELTY_TIME = 11111:
C2 = C1 - CELL_RESELECT_OFFSET
T is a timer, with 0 as the initial value. When a cell is listed by MS in the list of cells with maximum s
frame). When the cell is removed from the list, the associated T is reset.
After cell reselection, the T of original cell works as PENALTY_TIME. Namely, temporary offset is not
CELL_RESELECT_OFFSET (CRO) modifies cell reselecting time C2.
TEMPORARY_OFFSET (TO) is supplemented to C2from starting working of T to the prescribed time.
PENALTY_TIME is the time for TEMPORARY_OFFSET having effect on C2. When PENALTY_TIME = 11111
CELL_RESELECT_OFFSET, TEMPORARY_OFFSET, and PENALTY_TIME are cell reselection parameters.
lWhen the cell reselection parameter PI is 1, the MS is informed of receiving values of t
lIf PI is 0, the MS judges that the previous three parameters are 0, namely C2 = C1.
If the C2 of a cell (in the same location area as the serving cell) calculated by MS is greater than the
over 5s, the MS reselects to camp on the cell.
If the C2 of a cell (in different location area as the serving cell) calculated by MS is greater than the
reselect hysteresis, and this lasts for over 5s, the MS reselects to camp on the cell.
The interval between two reselections is at least 15s, and this avoids frequent cell reselection by MS.
C2 is formed on the combination of C1 and artificial offset parameters. The artificial offset paramete
on some cell. This balances the traffic of the network.
II.Format
1)The cell reselection offset (CRO) is in decimal, with unit of dB. It ranges from 0 to 63,
recommended value is 0.
2)The temporary offset (TO) is in decimal, with unit of dB. It ranges from 0 to 7, which m
recommended value is 0.
3)The penalty time (PT) is in decimal, with unit of second. It ranges from 0 to 31. The va
The value 31 is reserved for changing the effect direction of C2 by CRO. The recommended v
The previous parameters can be adjusted accordingly in the following three situations:
1)When the communication quality is bad due to heavy traffic or other causes, change th
(the cell is exclusive from the MS). For this situation, configure PT to 31, so TO is ineffective
the probability for MS to reselect the cell decreases. In addition, the equipment room opera
to the exclusive level of the cell by MS. The greater the exclusion is, the greater the CRO is.
2)For cells with low traffic and equipment of low utilization, change the parameters to e
this situation, configure CRO to 020 dB according to the priority. The higher the priority is,
as or a little greater than CRO. PT helps avoid over frequent cell reselection, the recommen
3)For cell with average traffic, configure CRO to 0, PT to 11111 so that C2 = C1. No artifi
IV.Precautions
In whatever situations, the CRO must not be greater than 30 dB, because over great CRO leads to uns
fluctuation.
4.3.7Cell Reselection Hysteresis (CRH)
I.Definition
CRH affects cell reselection of cross location area. The MS starts cell reselection if the following cond
lThe signal level of neighbor cell (in different location area) is greater than that of the
lThe
difference between the signal levels of the neighbor cell and the serving cell must
reselection hysteresis.
The difference is based on the cell reselection methods used by MS. If the MS reselects a cell with C2
II.Format
CRH is in decimal, with unit of dB. The range is 0 to 14, with step of 2 dB. The recommended value is
If the original cell and target cell belongs to different location areas, the MS must originate a locatio
the attenuation feature of radio channels, the C2 of two cells measured at the bordering area of neig
cells frequently. The interval between two reselections is over 15s, which is rather short for location
sharply, radio resources cannot be fully utilized.
During location updating, the MS cannot respond to paging, so the connection rate decreases. Adjust
signal flow overloads or location updating of cross location area is frequent, the cell reselection hyst
avoid abnormal coverage due to over large location area.
IV.Precautions
Do not configure CRH to 0 dB
cell_bar_access Cell selection priority Cell reselection state
0 Normal Normal
1 Barred Barred
0 Low Normal
1 Low Normal
Frequency Hopping Parameters

4.5.1Frequency Hopping Sequence Number
I.Definition
In a GSM network, the cell allocation (CA) means the set of carriers used by each cell, recorded as {R
absolute channel number. For each communication process, the set of carriers used by base station a
M1, , Mn - 1}. Wherein, Mi indicates the absolute channel number. Obviously MA is a subset of CA.
During a communication process, the air interface uses a carrier number, one element of MA. The va
exact element of MA. According to the frequency hopping algorithm in GSM regulation 05.02, the MAI
number (RFN), frequency hopping sequence number (HSN), and mobile allocation index offset (MAIO)
Wherein, the HSN determines two aspects:
lTrack of frequency points during frequency hopping
lThe asynchronous neighbor cells using the same MA can avoid continuous frequency col
HSNs.
II.Format
HSN is in decimal, ranging from 0 to 63, wherein:
l0: cyclic frequency hopping
l163: pseudo frequency hopping
You can choose any HSN in cells using frequency hopping, but you must ensure that the cells using sa
following paragraph is an exception:
In an 1X1 network, three cells under a base station use the same frequency group, but they are synch
three cells use the same HSN. You must plan MAIO properly to avoid frequency collision of the three
4.5.2Mobile Allocation
I.Definition
The mobile allocation (MA) in the GSM network indicates a frequency set for frequency hopping. Nam
communication frequency points of the cell performs transient in the set by MA according to rules.
The parameter MA determines all the elements in MA.
II.Format
MA is a set, with all GSM frequency points as its element, namely:
lFor GSM900 networks: 1124 and 9751023.
lFor GSM1800 networks: 512885
MA is configured according to network designing requirements.
IV.Precautions
Chinese GSM networks do not cover all available frequency bands of GSM system, so configure MA in a
The number of elements in each MA set cannot exceed 63.
The MA cannot include BCCH carriers.
The number of MA must not be multiples of 13 if all the following conditions are met:
lUsing DTX
lHSN = 0 (cyclic frequency hopping)
You must avoid SACCH to appear usually at the same frequency point.
4.5.3Mobile Allocation Index Offset
I.Definition
During communication, the air interface uses a carrier frequency, one element of MA set. MIO determ
the frequency hopping algorithm in GSM regulation 05.02, the MAI is the TDMA frame number (RN) or
sequence number (HSN), and mobile allocation index offset (MAIO). MAIO is an initial offset of MAI, a
same frequency carrier in the same time.
II.Format
MAIO ranges from 0 to 63.
MAIO is configured by equipment room operators.
IV.Precautions
The different cells using same group of MA must use consistent MAIO.
Using different MAIOs enables different sectors in the same location to use the same frequency group
Congestion Problems
This section introduces the methods to handle SDCCH congestion and TCH congestion, in which TCH congestion i
For this case, the real channels cannot be allocated to the MS, so the MS will fail to request the channels. The oth
I. Congestion Problem Solutions
l Congestion caused by heavy traffic
You can check if the SDCCH traffic and TCH traffic are normal through viewing traffic statistics. If the con
the capacity of the network. In addition, you can adopt traffic sharing technologies to ease the congesti
l SDCCH congestion caused by burst traffic
If the SDCCH congestion rate is high and the traffic is heavy but the TCH traffic is normal, the SDCCH con
railways and tunnel exits, because the BTSs are installed in remote places and the capacity of a BTS is sm
of MSs failing to capture a network will perform location update, which will result in SDCCH congestion
also occur easily. SDCCH congestion cannot be completely avoided, but some measures can be taken to
conversion between SDCCH and TCH.
l Congestion caused by TRX problems
When a carrier configured in a multi-TRX cell cannot provide services, the channel congestion will also
problem cannot be positioned, you should check if the antenna feeder connection is correct and if the
l Congestion caused by interference
The interference present across the radio interfaces will also cause congestion. In this case, you should
l Channel assignment failure caused by inconsistent coverage
If the concentric technology is not used, the transmit power of the TRXs within the same cell will be inc
will easily occur. To position this problem, you can check if the connection between the splitter and con
When a cell uses multiple transmitter antennas, inconsistent coverage will be inconsistent, which will re
transmitter antenna as consistent as possible through engineering adjustment.
In addition, if the transmitter antenna and the receiver antenna of a cell is not in the same plane or the
case, you can calibrate the antennas to solve the problem.
l Congestion caused improper data configuration
If the congestion is caused by improper location area planning, you can reduce the SDCCH congestion r
If the congestion is caused by the problems concerning SDCCH dynamic allocation, you can reduce the
For dual-band network, you can properly set the parameters (such as CRO, CBA, and cell reselection hys
If the timers, such as T3101, T3103, T3107, T3122, T3212, and T3111, are not properly set, SDCCH cong
Hereunder are the solutions to the previous problems.
You can ease the congestion caused by SDCCH dual allocation through reducing the T3101 to a smaller
time. To fully use the radio resources, therefore, you can reduce the T3101 value.
You can save the TCH resources through reducing the T3103 and T3107 to a rational value. Generally, T
The T3122 must be stopped once the MS receives an IMMEDIATE ASSIGN REJECT message. Only after t
request messages frequently, the RACH load and CCCH load will increase. To solve this problem, you ca
T3212 stands for the time limit value for periodical location update. You can ease the SDCCH load by in
T3111 is related to release latency. It is used for the deactivation of the latency channels after the majo
value of T3111 must be consistent with that of the T3110 at the MS side. Generally, it should be 2 seco
II. Congestion Cases
Case 1: SDCCH congestion caused by wrong LAC configuration
[Description]
A BTS is configured as S1/1/1. It is found that the SDCCH congestion rate for 2 cells reaches as high as 8%.
[Problem analysis and solution]
1) Through checking the measurement indexes for TCH and SDCCH, engineers found that the TCH t
However, the requests for SDCCH seizure are great, reaching 3032 times during busy hours. The SDCCH
2) The main reasons for SDCCH seizure include the messages sent before call setup, the messages
messages.
3) The TCH traffic is normal, the requests for TCH seizure (including handover) are normal (318 tim
may be caused by a large number of location update messages or short messages.
4) The LAC of the BTS is 0500, and the LACs of other cells of the surrounding cells are 0520. After c
busy hours were 298, the SDCCH traffic was 0.27Erl, and the congestion rate reduced to 0.
Case 2: SDCCH congestion caused by burst location updates
[Problem description]
The radio connected ratio of a local network is lower than average level. According to traffic statistics analysis, it i
1) Through analyzing traffic statistics, engineers found that the SDCCHs of the congested cells were
cell was configured with 8 SDCCHs. Therefore, the SDCCHs can be seized by 400 times, but the SDCCHs
2) As far as the registered traffic statistics items were concerned, most of the SDCCH seizures were
most of the BTSs were installed at the intersections of two railways. Therefore, it might be the burst loc
3) To verify if it was the burst location update that caused the congestion, engineers registered the
the five seconds. Through querying the train time table, engineers found that there were 4 to 5 trains p
location updates were generated in a short time. In this case, the congestion was caused.
Therefore, if the BTSs are installed at the railway intersections, you are suggested to enable the SDCCH dynamic a
Case 3: Great TCH congestion rate caused by the inconsistent tilt angles of two antennas under the same cell
It is found that the TCH congestion rate of a cell is great (greater than 5%) according to traffic statistics.
1) Through checking BSC traffic statistics, engineers found that it was the TCH seizure failure that d
2) Generally, TCH seizure failure is caused by TCH assignment failure. Through monitoring Abis inte
No.5 TRX, and the probability for the assignment failure rate for the No.4 TRX was near that for the No
3) Through checking the antenna feeder part, engineers found that the tile angle corresponding to
antenna for BCCH, because the antenna nuts were found loosen. Therefore, if the MS is far away from
to the MS when the MS starts a call, the TCH seizure failure will occur.
4) To solve the problem, you can enable the tilt angel of the TCH antenna and that of the BCCH ant
2% or lower.
Case 4: High TCH congestion rate caused by downlink interference
A cell of BTS is responsible for covering a large area of sea surface along the coast. According to the registered tra
congestion of the cell reached 10% at some time. However, no alarm was generated. All the interference bands fe
Because all the interference bands fell within the interference band1, the uplink interference is impossible. Cons
present along the coast, the probability for the channel numbers of the downlink areas and the cell to be interfe
congestion rate was improved. Through further optimizing the channel numbers, engineers found that the TCH c
caused by the downlink interference of some areas.
Handover Problems
The MS is always moving during conversation. To ensure channel quality, the MS must measure the quality of the
report to the BSC through the service cell. The BSC will perform radio link control according to the signal level an
new cell will replace the old cell to ensure the continuity of the service. The handover enables each cell to form a
I. Handover Problem Positioning Steps
1) Find out if the problem occurs at an individual cell or all cells and find out the characteristics of
co-BSC cells, or if they are co-MSC cells.
If the handover between two cells fails, you should focus on checking if the data of the two cells is corr
If the problem is found in all the neighbor cells of a cell, you should focus on checking of the data of th
If the problem is found in all the cells under the same BSC, you should focus on checking the data confi
If the problem is found in all the cells under the same MSC, the cooperation between the local exchang
the timer setting is irrational.
2) Check if the data has been modified before handover problems occur.
If the problem is found in an individual cell, you should focus on checking if the data configuration for t
If the problem is found in all the cells under the same BSC, you should focus on checking the data confi
If the problem is found in the cells under the same MSC, you should check if the data configuration for
3) Check if it is the hardware failure that causes the handover problem.
4) Register the related traffic statistics items, such as the handover performance measurement and
l Check if the TCH seizure of the problem cell is normal. For example, if the call dro
l Check if the outgoing handover success rate is normal.
l Find out the causes for the handover failure.
l Check if the radio handover success rate is normal.
5) Perform drive test for the problem cell and analyze the drive test signaling.
l Check if the uplink and downlink of the problem cells are balanced, because unba
l Check if the measurement report for the problem cell contains correct neighbor c
l Check if a call can hand over from a problem cell to a neighbor cell correctly and c
l Analyze if the signaling procedure for the handover is normal.
II. Handover Problem Analysis Methods
i) Handover cannot be initiated
If the MS is in a cell where the signal is poor, it cannot hand over to another cell. In this case, you should conside
Hereunder details the possible reasons:
l The handover threshold is set to a low value
For edge handover, the handover triggering condition is that the Rxlev must be smaller than the hando
of the neighbor cells will be far higher than that of the service cell. In this case, the handover cannot be
be resulted. The setting of the handover threshold depends on the coverage scope of the cell. You can
l Neighbor cell relationship is not set
Though the signal level in the neighbor cells of the service cell is high, the MS will not report the neighb
to a neighbor cell. Through performing cell reselection or dialing test, you can check the neighbor cell l
not found in the neighbor cell list, you should check if the correct neighbor cell relationship has been c
check if the strong BCCH numbers are in the service cell or in the neighbor cell list.
l Handover hysteresis is irrationally set
If the difference between the signal level of the handover candidate cell and that of the service cell is g
to a too great value, the handover is hard to be initiated.
l The best measurement time "N" and "P" are irrationally set
During normal handover, the MS uses N-P rules to list the handover candidate cells in a certain order. If
the best cell.
When there are two cells become the best cell alternately, the MS may find it hard to select a best cell
values of N and P and reduce the measurement time to make the handover decision more sensitive to
If the landform and the ground objects of the service cell are quite complicated, the signals received by
meet N-P rule, which will make the handover difficult.
ii) Handover problem caused by hardware failure
If the data configuration for the problem cell and the neighbor cells has not been modified recently but
caused by BTS hardware equipment.
If the cells sharing the same base station with the cell have similar problem, you should consider if the
If the problem is found in only one cell under the base station, you should consider if it is the hardware
To test the problems of this kind, you can disable some of the carriers. If the handover success rate retu
this carrier or if the CDU and antenna feeder part related to this carrier fails. If signals of a cell on the u
handover success rate will decrease.
To check if the signaling flow of the cell is normal and if the uplink Rxqual and downlink Rxqual are goo
means that the hardware equipment of the fails or serious interference is present in the cell. In this cas
iii) Handover problem caused by irrational data configuration
l For stand-alone networking mode, if the outgoing MSC or incoming MSC handover is abnormal,
you should also check if the data configuration for the opposite MSC and the local MSC has been modifi
l For co-MSC networking mode, if the handover is performed within the BSCs of different provide
cooperation between the BSCs is normal, and then check if the data configuration for the BSCs has bee
l If the abnormal handover is found at a cell only, you need to analyze the abnormal handover acc
If the incoming handover of a cell is abnormal, you need first check if the incoming handovers to this ce
low, or even the handover does not occur.
If all the incoming handovers to this cell is abnormal, you should check if the data configuration for this
cell and the data configured for other cells but is related to this cell. For example, the CGI of this cell ma
If there is only one incoming handover to a cell is abnormal but other incoming handovers to this cell a
should also check if the data configuration for the neighbor cells is correct. Furthermore, you should als
The methods to analyze the abnormal outgoing handovers are similar to the methods to analyze the ab
l Check the timers (such as T3105, Ny1, T3103, and T3142) related to the handover.
T3105 indicates the interval for continuous PHYSICAL INFORMATION to be sent to the MS. The network will start
any correct frame from the MS, the network will resend the PHYSICAL INFORMATION and restart the timer. A pie
of Ny1 and T3105 must be greater than the sum of T3124 and delta ("delta" indicates the interval between the e
otherwise the MS cannot perform successful handover.
T3124 is a timer waiting for the PHYSICAL INFORMATION from the network side during asynchronous handover. W
will start T3124. Upon receiving a piece of PHYSICAL INFORMATION, the MS will stop T3124. If the channel type a
675ms. For other cases, the T3124 is set to 320ms.
III. Handover Cases
Case 1: No handover candidate cell is available due to CGI error
The handover in an area is abnormal. When the MS moves from cell A to cell B, the signals in cell B are stronger t
to cell C, the MS hands over from cell A to cell C.
[Cause analysis]
If a cell can work as a service cell and can hand over to other cells, but the incoming handover is unavailable, you
[Problem solution]
1) Use the test MS to lock the BCCH numbers of cell B. The call is normal. The MS can hand over to
2) Make a call after locking the BCCH umber of any neighbor cell of cell B, and then force the MS to
command is seen in the drive test software.
3) The handover procedure requires the MS detecting the neighbor cell signals and reporting the d
report, the BSC must make the handover decision. If the handover conditions are met, the BSC should a
4) If the signals of cell B are far stronger than that of cell A and the handover conditions are met (t
errors occur during the activation of the target cell TCH.
5) If the cell B works as the target cell but the TCH cannot be activated, the data may be incorrectly
cell, so the TCH cannot be activated and no handover command can be found in the service cell.
6) The CGI error is found in cell B through data checking. The handover is normal after the CGI is ch
Case 2: Unbalanced path causes low handover success rate
The incoming BSC handover success rate is quite low for the two cells under a BTS, ranging from 10% to 30%.
[Cause analysis]
Generally, if the data problems, such as CGI error or intra-frequency interference, exists and if there is dead zone
signals, the incoming BSC handover success rate is low.
[Solution]
1) The cell data is found normal.
2) Through checking traffic statistics items, engineers found that all incoming cell handover success
3) Through drive test, engineers found that frequent handover attempts were made in the area 2k
made, call drop occurred immediately. During the handover, engineers found that the downlink level w
originating calls failed. For the answering calls, they can be connected but cannot be called out.
4) It is estimated that the CDU uplink channel loss is great, or the jumpers are incorrectly connecte
5) After changing the CDU, engineers found that the incoming handover success rate increased to
Case 3: Improper antenna planning causes low handover success rate
[Problem analysis]
The handover success rate among the three cells under a BTS is quite low according to traffic statistics. For the ha
than 30%.
[Cause analysis]
Generally, low handover success rate is caused by board failure, handover data error, or improper antenna plann
[Solution]
1) The BTS hardware is normal and no alarm concerning handover parameters is generated, so the
2) The BTS locates at the eastern side of a south-north road and is 700m away from the road. The a
directions and the open resident areas lying under a hill in the east respectively. Among the three cells,
engineers concentrated the antenna azimuth angles of the three cells in design. In this case, however, t
the coverage is provided by the side lobes and back lobes of the three cells. Therefore, when the MS is
the three cells are poor and fluctuating greatly. In addition, since the handover measurement time and
that's why the frequent handover failure occurs.
3) After setting the azimuth angles of the three cells to 60, 180, and 350, engineers found that t
Case 4: Problems concerning the cooperation of different carriers' equipment cause low outgoing BSC handove
There is a dual-band network in which the GSM900 MHz network and the GSM1800 MHz network are stand-alon
engineers found that the dual-band handover success rate was low; especially the success rate of the handover f
60% to 80%. However, the success rate of the handover from the GSM900 MHz network to the GSM1800 MHz ne
[Cause analysis]
For a dual-band network, if the problems concerning the cooperation of different carriers' equipment are found,
supports Phase 2+ and EFR.
[Solution]
1) Through using signaling analyzer to analyze the message flowing across the A-interface and E-int
Handover Reject message to the BSC of the GSM1800 MHz network when the BSC sent a Handover Req
2) The MSC of the GSM1800 MHz network sent a Prepare Handover message to the MSC of the GS
network sent back an Abort message.
3) Because the success rate of the handover from GSM900 MHz network to the GSM1800 MHz ne
message (from the GSM900 MSC to GSM1800 MSC) is half rate version 1, but the voice versions carried
version 1, full rate version 2, and half rate version 1, which belong to PHASE 2+. However, MSC of provi
4) Through modifying the MSC data of the circuit MSC data at the A-interface and selecting the ful
Handover message (from GSM1800 MSC to GSM900 MSC) are full rate 1 and 2. After that, the dual-ban
Call Drop Problems
For the GSM network, call drop is users' major worry and the call drop rate is an important index evaluating netw
I. Call Drop Resasons and Solutions
i) Call drop due to coverage reasons
[Reason analysis]
l Discontinuous coverage (dead zone)
For a single BTS, the quality of the signals at the edge of the station is quite poor, so the MS cannot han
another cell. In this case, the call drop occurs.
If the landform of the coverage areas is complex or fluctuates greatly, or the radio transmission environ
the signals will be barred. In this case, the coverage is discontinuous and call drop will occur.
l Poor indoor coverage
If the buildings in an area are densely populated, the signal attenuation is great. And if the walls of the
thick, the penetration loss is great and the indoor signal level is low. In this case, the call drop may easil
l Isolated island effect
As shown in Figure 8-13, the service cell forms an isolated island due to various reasons (for example, t
great). In this case, the MS still seizes the signals of the service cell A after moving to cell C, but the cell
define the neighbor cell C. At this time, if the MS still performs the handover according to the neighbor
by neighbor cell A, it cannot find a suitable cell. In this case, the call drop will occur.
l Small coverage
If the coverage is too small, the hardware equipment of a cell may fail. For example, the antenna is bar
failure occurs (the power amplifier part).
[Judgment methods]
First you should find out the areas where the coverage is inadequate according to user complaints, and then you
the drive test in a larger scope to check if the signal level and the handover are normal and if the call drop exists.
can employ the traffic statistics recorded at the OMC to check the BSC overall call drop rate and find out the cell w
drop rate. Furthermore, you can still make the analysis and judgment by referring to other traffic statistics items.
some ones:
l Power control performance measurement (to check if the mean uplink and downlink signal stren
l Rxlev performance measurement (to check if the ratio of the low Rxlev is too great)
l Cell performance measurement/inter-cell handover performance measurement (to check if the
the mean Rxlev are too low)
l Call drop performance measurement (to check if the signal level is too low during call drop and i
normal before call drop)
l Defined neighbor cell performance measurement (to position the cell with low mean signal leve
l Undefined neighbor cell performance measurement (to check if the undefined neighbor cells wi
level exist)
l Power control performance measurement (to measure the greatest TA value between the MS an
[Solutions]
1) Check the areas where the coverage is inadequate
You can find out the area where the coverage is inadequate through drive test. For an isolated BTS or th
in mountain areas that cannot form seamless coverage, you can add BTSs to these areas for seamless c
can improve the coverage through other means. For example, you can enhance the maximum transmit
BTS, change the antenna azimuth angle, change the antenna tilt, change the antenna height, and so on
should also analyze if the call drop is caused by landforms. Generally, call drop can easily occur at tunne
market, underground railway entrance, underground parking lot, and low-lying places. In this case, you
micro cell to solve the coverage problem.
2) Ensure indoor call quality
To ensure indoor call quality, you should make sure that the outdoor signals are strong enough. To stren
signals, you can increase the maximum BTS transmit power, change the antenna azimuth angle, change
angle, and change the antenna height, and so on. If the indoor call quality is still not improved remarka
consider adding BTSs. For improving the indoor coverage of office buildings and hotels, you can conside
indoor antenna distribution system.
3) For the cells having no neighbor cells, you can configure the neighbor cells for the cell so as to re
drop rate. To eliminate the isolation island effect, you can reduce the tilt angle of the BTS.
4) Eliminate hardware problems
You can check if there are hardware problems and if the coverage area is too small through drive test. If the call d
arises dramatically but all other indexes are normal, you should check if the neighbor cells of this cell work norm
the downlink problems may occur. For example, TRX problem, diversity unit problem, and antenna problem are c
the uplink fails, the outgoing handover failure rate of the old cell will be high.)
ii) Call drop due to handover reasons
[Reason analysis]
l Irrational parameter configuration
If the signal level at the cross-area of two cells is quite low, the level of the handover candidate cell is to
handover threshold is too low, some MSs will hand over to the neighbor cell when the signal level of th
higher than that of the service cell. If the signal level of the neighbor cell deteriorates dramatically just
handover, the call drop will occur if no suitable cell is available for the handover.
l Incomplete neighbor cell definition
If the neighbor cell definition is incomplete, the MS will hold the conversation in the existing cells until
the edges of the cell but cannot hand over to a stronger cell. In this case, the call drop will occur.
l Neighbor cells with same BCCH and same BSIC exist.
l Traffic congestion
If the traffic is unbalance, no TCH will be available in the target cell. In this case, the handover failure w
l BTS clock lost synchronization
If the BTS lost synchronization, the frequency offset will go beyond the requirement. In this case, the ca
if handover fails.
l T3103 expiry
The T3103 will be started when the network sends a handover command. Upon the reception of the message to
handover or the message to remove the command, the T3103 will stop. T3103 is used to hold the channel long e
MS to return to the old channel. If the T3103 is set to a too small value, the MS cannot necessarily return to the
this case, call drop may occur during handover.
[Judgment methods]
You can judge if the cells with low handover success rate, frequent re-establishment failures, and high call drop ra
analyzing traffic statistics indexes. After the judgment, you can find out what causes the handover. For example, t
downlink Rxlev can cause the handover; the uplink and downlink Rxqual can cause the handover; power budget
handover; call direct retry can cause handover; and also handover can be initiated by traffic reasons.
To check if the BTS clock runs normally, you can check if the any alarm is generated for the BTS clock. If necessary
correct the BTS clock to eliminate clock problem. You can check if there is handover problem through drive test. I
problem cell, you should perform drive near the cell for several times. Hereunder lists the indexes concerning cal
l Inter-cell handover performance measurement (frequent handover failures, frequent re-establis
l Inter-cell handover performance measurement (frequent handovers, high re-establishment rate
l Undefined neighbor cell performance measurement (the undefined neighbor cell level and the n
measurement report go beyond the standard)
l Outgoing cell handover performance measurement (find out the reasons for low outgoing cell h
handover target cell)
l Low incoming cell handover success rate; the cell handover parameters are improperly set; the t
congested.
l TCH performance measurement (the handover times are not proportional to the TCH call seizure
handover happens too frequent)
[Solution]
1) Check the parameters affecting the handover. For example, you can check the hierarchical and le
handover threshold, each handover hysteresis, handover time, handover duration, the minimum acces
handover candidate cell, and so on.
2) If the call drop is caused by unbalance traffic volume or if the call drop occurs due to no handov
available at the target BTS, you can solve the problem by adjusting the traffic volume. For example, you
project parameters, such as antenna tilt and antenna azimuth angle, to control the coverage scope of a
the traffic volume, you can use CRO to guide the MS to camp on other idle cells, or you can set the hier
priority to guide the MS to hand over to the idle cell. In addition, you can solve the problem by expand
directly.
3) Calibrate the problem BTS clock to enable the synchronization of the clock.
iii) Call drop due to interference reasons
[Reason analysis]
If the MS receives strong same-frequency interference signals or strong neighbor frequency interference signals i
the bit error rate will deteriorate. In this case, the MS cannot demodulate the BSIC code of the neighbor cells acc
cannot receive the measurement report from the MS correctly. As a result, the conversation will be interfered, th
become poor, and call drop will occur.
[Judgment methods]
The interference may be from the network itself or the outside network, or it may exist in the uplink signals or do
The following methods can be used to position the interference.
l Find out the cells might be interfered through checking traffic statistics.
l Perform the call drive test for the areas that might be interfered and check the uplink and down
according to user complaint. You can find out if there is a place where the signal is strong but the call q
through drive test tools. In addition, you can use a test MS to perform dialing test to check if a channel
interfered.
l Check the frequency planning to see if same-frequency interference and neighbor frequency int
in the area where the frequency is improperly planned.
l Adjust the channel numbers that might be interfered to see if the interference can be avoided o
l Exclude the interference caused by equipment.
l If the previous methods fail to eliminate the interference, you can use the spectrum analyzer to
frequencies to find out the interfered channel number and the interference source.
Hereunder lists several traffic statistics indexes used for interference analysis:
l Interference band
You can check the uplink interference through analyzing the interference band in the traffic statistics. If
appears at the interference bands 3-5, the interference is present. If it is intra-network interference, it w
the traffic volume grows. Generally, if it is outside interference, it is not related to traffic volume. It mus
that the interference bands are reported to the BSC by the BTS TRX channel (when in idle mode) throug
indication messages. If the current channel is busy and cannot report RF resource indication message, y
consider the traffic volume for the measuring the interference bands.
l Rxlev performance measurement
The Rxlev performance measurement provides the matrix relationship between the signal level and qu
level is high but the quality is poor, it means that the interference (same-frequency interference, intra-f
interference, and outside interference) is present at the channel numbers of the TRX board.
l Poor quality handover ratio
The cell performance measurement, inter-cell handover performance measurement, or the outgoing ce
performance measurement records the outgoing handover attempt times. If the frequent handover is c
signal quality, it means that the interference is present.
l Rxqual performance measurement
It is related to the mean Rxlev and Rxqual during call drop.
l Call drop performance measurement
It records the mean Rxlev and Rxqual during call drop.
l Frequent handover failures and frequent re-establishment failures
It means that the interference may be present in the target cell.
[Solutions]
1) Check the interfered road and the distribution of signal quality through dive test. As far as the a
are concerned, you can adjust the BTS transmit power and antenna tilt of the related cells or adjust the
planning to avoid the interference.
2) Use DTX technology, frequency hopping technology, power control, and diversity technology
These technologies can be used to reduce the system noise and enhance anti-interference capacity of t
divided into uplink DTX and downlink DTX. In this case, the transmit time can be reduced and the interf
the system can also be reduced. However, you should adjust the DTX according to the actual radio envi
neighbor cell relationship. When signals received by the MS are poor, the use of the DTX will result in c
downlink DTX is enabled, the BTS will increase its transmit power after the call is established. During th
however, the BTS will reduce its transmit power. In this case, the interference against other BTSs will be
interference is present near the BTS, the downlink DTX will deteriorate the conversation quality. When
its transmit power, the conversation quality will decrease or the call drop may even occur in the areas w
low butSolve
3) the interference signal
the equipment is strong.such as the self-excitation of TRX boards and the antenna demo
problems,
interference.
4) Exclude the outside interference.
iv) Call drop due to antenna feeder reasons
[Reason analysis]
l Engineering problem may be one of the reasons. For example, if the transmit antennas between
inversely connected, the level of the uplink signal will be far poorer than that of the downlink signal. In
drop, one-way audio, and call difficulty will be found in the areas far away from the base station.
l If polarization antennas are used, a cell had two sets of antennas. If the tilt angles of the two an
inconsistent with each other, the call drop will occur.
If a directional cell has a master antenna and a diversity antenna, the BCCH and the SDCCH of the cell m
transmitted through the two antennas respectively. If the tilt angles of the two antennas are different,
scope of the two antennas will be different. In this case, the MS can receive BCCH signals but cannot se
when starting a call. Thus the call drop is resulted.
l If the azimuth angles of the two antennas are inconsistent with each other, call drop may also oc
MS can receive the SDCCH signals, but it may be assigned with the TCH. In this case, the call drop will o
l The problems concerning antenna feeder will also cause call drop. For example, if the antenna is
water penetrates into the antenna, or connector problem is present, the transmitter power and the rec
will decrease. In this case, the call drop will occur. To confirm the problem, you can check the standing w
[Problem positioning and solution]
1) Check if any alarm concerning the combiner, CDU, tower amplifier, and standing wave is generat
the BTS boards are normal in the OMC.
2) Analyze if the path balance is realized according to traffic statistics.
3) Further analyze if the path balance is realized through monitoring the messages sent across the
4) Perform drive test and dialing test. During drive test, you can check if the BCCH numbers of the
consistent with the planned ones, namely, if the transmit antenna of the antenna is correctly installed.
5) Check and test the on-site BTSs. Here the installation of the azimuth angle and the tilt angle of t
be checked. In addition, you should also check if the feeder and jumper are correctly connected, if ther
problem, and if the feeder is damaged. Furthermore, you must still check if the standing wave is norma
6) Judge if it is BTS hardware that causes path unbalance and call drop. To solve hardware problem
change the components that may have problems or disable other TRXs in the cell. To find out the probl
position the problem through dialing test. Once a problem hardware component is found, you must rep
sound one. If no sound one is available, you must shut down the problem hardware component to prev
affecting network quality.
Hereunder lists several traffic statistics items for path balance analysis:
l Path balance measurement (to analyze if the path balance is realized)
l Call drop performance measurement (to analyze the uplink and downlink level and quality durin
l Power control performance measurement (to analyze mean Rxlev on the uplink and downlink)
v) Call drop due to transmission reasons
If the transmission quality across the Abis interface and A-interface may be not good and stable, call drop may oc
following methods can be used to solve the problem:
1) Check the transmission alarm and board alarm and analyze if there is transmission intermittent
2) Check the transmission channel, test the bit error rate, check 2M connectors, and check if the eq
grounding is rational to ensure stable transmission quality and reduce call drop rate.
3) Check the traffic statistics to see if the frequent call drop is caused by transmission problems. Es
should check TCH performance measurement, because it can indicate if the A-interface failures during
normal, if the TCH utilization is normal, and if the ground link call drop times are great.
vi) Call drop due to parameter reasons
Here you should focus on checking if the parameters related to call drop are irrationally set. If the following param
irrationally set, the call drop may be resulted.
l Radio link failure counter
This parameter acts on the downlink. When the MS fails to decode the SACCH, it will use this paramete
to disconnect the call. If this parameter is set to a too small value, the radio link failures will easily occu
drop. For dead zones or the areas where the call drop frequently happens, you are recommended to se
to a greater value.
When changing the radio link failure counter, you should change the corresponding T3109. The T3109 m
value great enough for the MS to detect a radio link failure. For example, if the value of the radio link fa
16 (about 8 seconds), the value of T3109 must be greater than 8 seconds (you can set T3109 to 9 secon
seconds).
l SACCH multiframe number
This parameter acts on the uplink. The BTS uses this parameter to notify the radio link connection failur
BSS. The BSS side judges the radio link failure according to the bit error rate on the uplink SACCH. If this
to a too small value, the radio link failure will happen frequently and the call drop rate will be resulted.
l Access control parameters
The access control parameters include the Minimum RACH Rxlev, RACH busy threshold, and so on. If th
parameters are irrationally set, the call drop will be easily resulted.
l T3101, T3107
T3101 is started when the BSC sends a CHANNEL ACTIVATE message to the BTS. It stops when an ESTAB
message is received. This timer monitors the immediate assignment procedure. If T3101 expires, the al
will be removed.
T3107 is started when the BSC sends an ASSIGNMENT COMMAND message to the BTS. Once the BSC re
ASSIGNMENT COMPLETE message from the BTS, this timer will reset. T3107 is used to hold the channe
that the MS can return to the old channel. Or it can also be used by the MS to release a channel.
If the two timers are set to a too small value, the system will not have enough time to send the ASSIGN
message to the BSC. In this case, the call drop will occur if the timer expires.
l T200; N200
T200 is an important timer used for the LAPDm (Link Access Procedure on the Dm channel). It prevents
from occurring when the data is transferred across the data link layer. In GSM system, the messages tra
radio interfaces can be divided into two types: the messages needing opposite acknowledgement and t
needing opposite acknowledgement.
For the messages needing opposite acknowledgement, a T200 must be started once the message is sen
acknowledgement is not received after a period of time, the message should be retransmitted. In this c
must be restarted. If the retransmission times exceed the maximum allowed times, the message will no
retransmitted and the link will be released. That is, this call drops. N200 is the maximum retransmission
T200 and N200 have different types depending on channel types (TCH full rate, TCH half rate, and SDCC
types (signaling and messages). The given channel type and service type matches a pair of T200 and N2
The call drop rate can be reduced if the message is retransmitted as early as possible before the opposi
acknowledgement is received. That is, the value of T200 must be set as small as possible and the value
set as great as possible. However, the T200 cannot be set to a too small value and the N200 cannot be
value. If the opposite party has acknowledged that the link had been removed, the retransmission will
Therefore, to reduce the call drop rate, you can adjust the T200 and N200 according to actual radio con
II. Call Drop Cases
Case 1: Call drop caused by frequency hopping collision
[Problem analysis]
A BTS uses 1 x 3 RF frequency hopping. After capacity expansion, the TCH allocation failure rate is still high due to
problems. In addition, the TCH call drop rate and incoming handover failure rate are high. The SDCCH call drop ra
[Problem positioning and solution]
Because high call drop rate and high incoming handover failure rate come together with the TCH allocation rate,
that the problem may arise during TCH assignment or the channel numbers or timeslots seized by the call are int
unstable. Because the SDCCH call drop rate is normal, it can be judged that the probability for the BCCH carriers a
numbers to the interfered are small, but the non-BCCH carriers and non-BCCH numbers may be greatly interfered
Through checking the hardware, antenna feeder, and transmission, engineers found no problem. According to dr
engineers found that the signal level was high but the quality was poor. Through on-site dialing test, engineers fo
conversation quality was poor. Through checking engineering parameters, engineers found that the MAIO of the
the same as that of the old carrier. Therefore, it can be judged that the call drop was caused by the frequency ho
After modifying the MAIO, engineers found that call drop rate became normal.
Case 2: Call drop caused by isolated island effect
Users complained that call drop always occurred above the fifth floor of a building.
[Problem analysis]
1) Through on-site test, engineers found that call drop and noise existed here. As far as the test MS
it was always in the service area of the other BTS (hereunder called BTS B) other than the local BTS (her
BTS C) before the call drop.
2) It is estimated that the service cell belongs to BTS B, which is 3-4 kilometers away from the build
can be judged that the signals from the BTS B are reflected signals. As a result, an area similar to an isol
formed.
3) Through checking data configuration, engineers found that only the cell 2 of BTS A has the neigh
relationship with BTS B. Therefore, when the MS is using the signals in cell 2 of the BTS B, if the signals
were strong, and if the cell 2 of BTS B has no neighbor cell relationship with the cell 3 of the BTS A, the
be performed.
The signals from the cell 2 of BTS B are reflected many times. Therefore, when signals (from BTS B) rece
became poor dramatically, emergent handover may be initiated. In this case, however, either the cell 2
BTS A is not an ideal candidate cell for the cell 2 of BTS B. As a result, the MS may hand over to other BT
called BTS C), but the MS cannot receive the signals from BTS C. Therefore, call drop occurs.
[Solution]
You are recommended to change the data in the BA1 (BCCH) list, BA2 (SACCH) list, and neighbor cell relationship
you can configure the cell 3 of BTS A as the neighbor cell of cell 2 of BTS B. To eliminate the isolated island effect,
further optimize the engineering parameters. After that, the call drop problem can be solved.
Case 3: Reduce call drop rate through optimizing handover parameters
The drive test in an area found that the call drop rate at a cave near the BTS high because the handover cannot b
due time.
The cave is near the BTS. The signal level of the target cell is about -80dBm in the cave, but the signal level of the
below -100dBm. The downlink power of the two cells outside the cave is good, so the handover cannot be initiat
signal level deteriorates dramatically in the cave, so the call drop occurs before the measurement time is arriving
To reduce the call drop rate, you can optimize and adjust the handover parameters:
1) If no ping-pong handover is present and the conversation is continuous, you can make the PBGT
happen as easily as possible.
2) Set the threshold to trigger the emergent handover rationally so that the emergent handover ca
before call drop.
For the parameter modification, see
Handover parameter optimization
Parameter Name
PBGT handover measurement time
PBGT handover duration
PBGT handover threshold
Uplink quality threshold for emergent handover
Minimum downlink power for handover candidate cell
Case 4: Call drop caused by clock problem

The cell A of an 1800MHz network has been cutover. After the establishment of a cell at site B, the calls made in
over to the GSM900 MHz cell that shares the same BTS site drops in the GSM900 MHz cell. And the call drop rate
Engineers find that the clock of the GSM900 MHz BTS and that of the GSM1800 MHz BTS are asynchronous. Whe
established on the GSM1800 MHz cell intend to hand over to the GSM900 MHz cell, the drive test data shows th
dramatically first, and then gradually disappears to none. If the handover is from a GSM900 MHz cell to a GSM18
phenomenon is also present. Through monitoring signaling, engineers find that the conversation held several sec
call drop is just process for call re-establishment. However, the test MS shows that the call has been handed over
MHz cell. Therefore, it can be judged that the clocks are seriously asynchronous. To solve this problem, the carrie
the GSM900 equipment provider cooperate with each other on clock calibration. After that, the abnormal call dr
Therefore, for dual-band handover, the clock of the GSM900 MHz BTS and that of the GSM1800 MHz BTS must b
Before Modification
After Modification
Power Control and Related Parameters
4.9.1 Maximum Transmit Power of MS (MSTXPWRMX)
I. Definition
The transmit power of MS in communication is controlled by BTS. According to the uplink signal strength and qua
& Note:
In any situation, power control is prior to related handover for BSS. Only when the BSS fails to improve uplink sig
To reduce interference between neighbor cells, the power control of MS is restricted. Namely, the BTS controls M
MSTXPWRMX is the maximum transmit power of MS controlled by BTS.
II. Format
MSTXPWRMX ranges from 0 to 31.
The dBm values corresponding to GSM900 and GSM1800 cells are different:
l The 32 maximum transmit power control classes for GSM900 are {39, 39, 39, 37, 35, 33, 31, 29,
l The 32 maximum transmit power control classes for GSM900 are {30, 28, 26, 24, 22, 20, 18, 16,
III. Configuration and Influence
Configuring MSTXPWRMX helps control interferences between neighbor cells, because:
l If MSTXPWRMX is over great, the interference between neighbor cells increases.
l If MSTXPWRMX is over small, the voice quality declines and improper handover might occur.
4.9.2 Received Level Threshold of Downlink Power Increment (LDR)
I. Definition
When the downlink received level of the serving cell is smaller than a threshold, the network must start power co
MS.
The received level threshold of downlink power increment defines the downlink received level threshold. When t
increase its transmit power.
The parameter N1 means that at lease N1 sampling points must be measured before starting handover algorithm
The parameter P1 means the level of at least P1 sampling points in N1 sampling points is smaller than the thresh
II. Format
N1 ranges from 1 to 32.
P1 ranges from 1 to 32.
The received level is between 60 dBm and 80 dBm in a GSM network, so configure received level threshold of
N1 is related to propagation quality of radio channels within cell coverage range. To reduce influence by attenuati
Configure P1 to about 2/3 of N1.
4.9.3 Received Level Threshold of Uplink Power Increment (LUR)
I. Definition
When the uplink received level of the serving cell is smaller than a threshold, the network must start power cont
The received level threshold of uplink power increment defines the uplink received level threshold. When the up
transmit power.
The parameter P1 means the level of at least P1 sampling points in N1 sampling points is smaller than the thresh
II. Format
4.9.4 Received Quality Threshold of Downlink Power Increment (LDR)
I. Definition
When the downlink received quality of the serving cell is smaller than a threshold, the network must start power
The received quality threshold of downlink power increment defines the downlink received level threshold. Whe
increase its transmit power.
The parameter P3 means the quality of at least P3 sampling points in N3 sampling points is smaller than the thre
II. Format
It ranges from 0 to 7, the voice quality grade.
The received quality is 0 to 2 of quality grade in a GSM network, so configure received quality threshold of down
4.9.5 Received Quality Threshold of Uplink Power Increment (LUR)
I. Definition
When the uplink received quality of the serving cell is smaller than a threshold, the network must start power co
The received quality threshold of uplink power increment defines the uplink received quality threshold. When th
transmit power of MS.
The parameter P3 means the quality of at least P3 sampling points in N3 sampling points is smaller than the thre
II. Format
The received quality is 0 to 2 of quality grade in a GSM network, so configure received quality threshold of uplink
4.9.6 Received Level Threshold of Downlink Power Decrement (UDR)
I. Definition
When the downlink received level of the serving cell is greater than a threshold, the network must start power co
channels.
The received level threshold of downlink power decrement defines the downlink received level threshold. When
decrease its transmit power.
The parameter P2 means the level of at least P2 sampling points in N2 sampling points is greater than the thresh
II. Format
4.9.7 Received Level Threshold of Uplink Power Decrement (UUR)
I. Definition
When the uplink received level of the serving cell is greater than a threshold, the network must start power cont
The received level threshold of uplink power decrement defines the uplink received level threshold. When the up
The parameter P2 means the level of at least P2 sampling points in N2 sampling points is greater than the thresh
II. Format
4.9.8 Received Quality Threshold of Downlink Power Decrement (UDR)
I. Definition
When the downlink received quality of the serving cell is greater than a threshold, the network must start power
The received quality threshold of downlink power decrement defines the downlink received quality threshold. W
decrease transmit power of MS.
The parameter P4 means the quality of at least P4 sampling points in N2 sampling points is greater than the thre
II. Format
The received quality is 0 to 2 of quality grade in a GSM network, so configure received quality threshold of down
4.9.9 Received Quality Threshold of Uplink Power Decrement (UUR)
I. Definition
When the uplink received quality of the serving cell is greater than a threshold, the network must start power co
The received quality threshold of uplink power decrement defines the uplink received quality threshold. When th
The parameter P4 means the quality of at least P4 sampling points in N4 sampling points is greater than the thre
II. Format
The received quality is 0 to 2 of quality grade in a GSM network, so configure received quality threshold of uplink
4.9.10 Power Control Interval (INT)
I. Definition
It takes a period from beginning of power control to detection of effect of power control. Therefore an interval m
even call drop occurs.
The parameter power control interval (INT) configures the minimum interval between two continuous times of p
II. Format
It ranges from 0 to 31s.
According to frame structure of GSM network, configure INT to about 3s.
IV. Precautions
INT cannot be smaller than 1s, and otherwise the system becomes unstable.
4.9.11 Power Increment Step (INC)
I. Definition
The INC indicates the power increment of MS or base station in power control.
II. Format
The range of INC is 2 dB, 4 dB, or 6 dB.
The recommended value is 4 dB.
4.9.12 Power Decrement Step (RED)
I. Definition
The RED indicates the power decrement of MS or base station in power control.
II. Format
The range of RED is 2 dB or 4 dB.
The recommended value of RED is 2 dB.
Checking the Parameter Settings for DCR Huawei 2G
The parameter settings on the BSC side and MSC side may affect the TCH
call drop rate. You should check the settings of the following parameters for
a cell with a high TCH call drop rate. See Case 5: Reduction of Call Drops by
Optimizing Handover Parameters and Case 12: Increase in Call Drop Rate Due to
Change of TR1N on the MSC Side.
1. SACCH Multi-Frames
This parameter determines whether an uplink radio link is faulty. Each time the
BTS fails to decode the measurement report on the SACCH from the MS, the
counter decreases by 1. Each time the BTS successfully decodes the
measurement report on the SACCH, the counter increases by 2. When the
value of this counter is 0, the BTS regards the radio link as faulty. In the
traffic measurement, if there are many call drops (M3101A) related to radio
link failure, you can infer that the radio propagation conditions are poor. In
this case, you can set this parameter to a greater value.
2. Radio Link Timeout
This parameter determines whether a downlink radio link is faulty. Each
time the BTS fails to decode the measurement report sent over the SACCH
by the MS, the counter decreases by 1. Each time the BTS successfully
decodes the measurement report sent over the SACCH, the counter
increases by 2. When the value of this parameter is 0, the BTS regards the
radio link as faulty. In the traffic measurement, if there are many call drops
(M3101A) related to radio link failure, you can infer that the radio
propagation conditions are poor. In this case, you can set this parameter to
a greater value.
3. RXLEV_ACCESS_MIN
This parameter specifies the minimum receive level of an MS to access the BSS. If
this parameter is set to a too small value, some MSs with low receive levels
may access the network and call drops are likely to occur. You can set this
parameter to a great value to reduce the TCH call drop rate. The counters
such as call setup success rate and the counters related to traffic volume,
however, are accordingly affected.
4. RACH Min.Access Level
This parameter determines whether an MS can access the network over the RACH.
If this parameter is set to a too small value, some MSs with low signal levels
may access the network and call drops are likely to occur. You can set this
parameter to a great value to reduce the TCH call drop rate. The counters
such as call setup success rate and paging success rate, however, are
affected.
5. Min DL Power on HO Candidate Cell and Min Access Level Offset
The sum of the values of the two parameters specifies the minimum
downlink receive level of a candidate neighboring cell for a handover. If this
parameter is set to a too great value, some desired cells may be excluded from
the candidate cells; if this parameter is set to a too small value, an unwanted cell
may become the candidate cell. Both conditions may lead to the increase of call
drops.
6. Timer T3103 series
Timer T3101 series consists of T3103A, T3103C, and T8. These timers are
started to wait for a handover complete message. If the lengths of the
timers are set to small values, probably no message is received when timer
T3103 series expires. In this case, the BSC considers that the radio link in
the originating cell is faulty. Then, the BSC releases the channel in the
originating cell. Thus, call drops occur. In the traffic measurement, if many
call drops are related to handovers (CM331: Call Drops on Radio Interface
in Handover State), you can set this parameter to a greater value. If this
parameter is set to a too great value, channel resources are wasted and
measurement report on the SACCH, the counter increases by 2. When the
value of this counter is 0, the BTS regards the radio link as faulty. In the
traffic measurement, if there are many call drops (M3101A) related to radio
link failure, you can infer that the radio propagation conditions are poor. In
this case, you can set this parameter to a greater value.
7. Timer T3109
This parameter specifies the period for waiting for a Release Indication
message after the BSC sends a Channel Release message to the BTS. If
this parameter is set to a too small value, the link may be released before
the Release Indication message is received. As a result, a call drop occurs.
You can set this parameter to a greater value to reduce the TCH call drop
rate. It is recommended that timer T3109 be set to 12 seconds longer than
timer Radio Link Timeout.
8. Timer T3111
This parameter specifies the interval between the time that the main
signaling link is disconnected and the time that a channel is deactivated.
The purpose is to reserve a period of time for repeated link disconnections. If this
timer is set to a too small value, a channel may be deactivated too early.
Thus, call drops increase.
7. Timer T3109
This parameter specifies the period for waiting for a Release Indication
message after the BSC sends a Channel Release message to the BTS. If
this parameter is set to a too small value, the link may be released before
the Release Indication message is received. As a result, a call drop occurs.
You can set this parameter to a greater value to reduce the TCH call drop
rate. It is recommended that timer T3109 be set to 12 seconds longer than
timer Radio Link Timeout.
8. Timer T3111
This parameter specifies the interval between the time that the main
signaling link is disconnected and the time that a channel is deactivated.
The purpose is to reserve a period of time for repeated link disconnections. If this
timer is set to a too small value, a channel may be deactivated too early.
Thus, call drops increase.
11. Call Reestablishment Forbidden
This parameter specifies whether to allow call reestablishment. In case of
burst interference or radio link failure due to blind areas caused by high
buildings, call drops occur. In this case, MSs can initiate the call
reestablishment procedure to restore communication. To reduce the TCH
call drop rate, you can set this parameter to No to allow call
reestablishment. In certain conditions, allowing call reestablishment greatly
reduces the TCH call drop rate. Call reestablishment lasts for a long time, and
therefore some subscribers cannot wait and hang up. This affects user experience.
12. Parameters related to edge handover
When the receive level drops greatly, an edge handover cannot be
performed in time in any of the following conditions: The parameter Edge
HO UL RX_LEV Threshold or Edge HO DL RX_LEV Threshold is set to a
small value; the parameter Inter-cell HO Hysteresis is set to a great value;
the parameters Edge HO Watch Time and Edge HO AdjCell Watch Time
are set to great values; the parameters Edge HO Valid Time and Edge HO
AdjCell Valid Time are set to great values. As a result, a call drop occurs.
To reduce the TCH call drop rate, you can appropriately set these
parameters so that edge handovers can be performed in time to avoid call
drops.
13. Parameters related to BQ handover
When the signal quality deteriorates, a BQ handover cannot be performed
in time in any of the following conditions: The parameters
ULQuaLimitAMRFR, ULQuaLimitAMRHR, UL Qual. Threshold,
DLQuaLimitAMRFR, DLQuaLimitAMRHR, and DL Qual. Threshold are
set to great values; the parameter BQ HO Margin is set to a small value;
the parameter Inter-cell HO Hysteresis is set to a great value. As a result,
call drops occur. To reduce the TCH call drop rate, you should appropriately
set these parameters so that BQ handovers can be performed in time to
avoid call drops.
14. Parameters related to interference handover
If the parameters RXQUAL1 to RXQUAL12 are set to great values or if the
RXLEVOff parameter is set to a great value, strong interference may occur.
In this case, if interference handovers are not performed in time, call drops
occur. To reduce the TCH call drop rate, you can appropriately set these
parameters so that interference handovers can be performed in time to
avoid call drops. If the parameters RXQUAL1 to RXQUAL12 are set to
small values, the number of handovers due to other causes increases
greatly, thus affecting the handover success rate.
15. Parameters related to concentric cell handover
A call at the edge of the overlaid subcell cannot be handed over to the
underlaid subcell in any of the following conditions: In the case of a normal
concentric cell, the parameters RX_LEV Threshold and RX_LEV
Hysteresis are set to great values; in the case of an enhanced concentric
cell, the parameter OtoU HO Received Level Threshold is set to a great
value. As a result, a call drop is likely to occur. If the Call Drop Ratio on TCH
on the TRX in the OverLaid Subcell (RM330a) is high, you can
appropriately set these parameters so that calls at the edge of the overlaid
subcell can be handed over to the underlaid subcell in time.
When a call in the underlaid subcell has interference, the call cannot be
handed over to the overlaid subcell if the RX_QUAL for UO HO Allowed
parameter is set to Yes and the RX_QUAL Threshold parameter is set to a
great value. Thus, a call drop occurs. If the Call Drop Ratio on TCH on the
TRX in the Underlaid Subcell (RM330) is high, you can set these
parameters properly so that the call can be handed over to the overlaid
subcell at the earliest.
16. Parameters related to power control
If the power control level and quality threshold are set to small values, call
drops are likely to occur because of low signal level or bad voice quality.
17. T200 and N200
If the parameters T200 FACCH/F, T200 FACCH/H, N200 of FACCH/Full
rate, and N200 of FACCH/Half rate are set to small values, data links are
disconnected too early. Thus, all drops are likely to occur. If call drops occur
because of T200 expiry, you can increase the values of T200 and N200
properly.
18. Neighboring cell relations
If the neighboring cells configured in the BA2 table are incomplete, call
drops are likely to occur in the case of no suitable neighboring cell for
handover and progressive deterioration in the voice quality. Neighboring cell
relations should be configured completely on the basis of the drive test data
and electronic map (for example, Nastar) to minimize the call drops due to
no available neighboring cells.
19. MAIO
If frequency hopping (FH) is applied in a cell and the MAIO is set
inappropriately (for example, different TRXs serving the same cell have the
same MAIO), frequency collision may occur during FH. Thus, the TCH call
drop rate increases.
20. Disconnect Handover Protect Timer
This parameter is a software parameter of the BSC. After receiving a
DISCONNECT message from an MS, the BSC cannot hand over the MS
within the period specified by this parameter. Therefore, the following case
can be avoided: After being handed over to the target cell, the MS cannot
be put on hook because it does not receive a release acknowledgement
message. You are advised to set this parameter properly.
21. TR1N
This parameter should be set on the MSC side. It is used to avoid the
retransmission of short messages. When this parameter is set to a too great
value, the MSC does not send a CLEAR CMD message if the MS receives
a short message during link disconnection. As a result, the MS sends the
BTS a DISC message to disconnect layer 2 connection. After receiving the
DISC message, the BTS sends a REL_IND message to the BSC. Then, the
BSC sends a CLEAR REQ message to the MSC and the number of call
drops is incremented by one.
22. Software Parameter 13 and MAX TA
When the parameter Software Parameter 13 is enabled and the parameter MAX
TA is set to a too small value, the channel is released when the TA of a call exceeds
the MAX TA. In this case, call drops occur. It is recommended that the
parameter Software Parameter 13 should not be enabled.
23. Directly Magnifier Site Flag
If a BTS is installed with repeaters, the handover between repeaters can only
be asynchronous because the distance between repeaters is long. If
synchronous handovers are performed, the handovers may fail and thus many
call drops occur. Therefore, when a BTS is installed with repeaters, the
parameter Directly Magnifier Site Flag should be set to Yes to avoid
synchronous handovers between cells under the same BTS.
Vendor Tech Resource Type

Huawei 3G UL CE
Huawei 3G DL CE
Huawei 3G UL Power
Huawei 3G DL Power
Huawei 3G UL IuB
Huawei 3G DL IuB
Huawei 3G Code
NSN 3G UL CE
NSN 3G DL CE
NSN 3G UL Power
NSN 3G DL Power
NSN 3G IuB
NSN 3G Code
Huawei 2G SDCCH
Huawei 2G TCH
Huawei 2G TBF
Huawei 2G PDCH
Huawei 2G Abis
Nokia 2G SDCCH
Nokia 2G TCH
Nokia 2G PDCH
Nokia 2G Abis
Siemens 2G SDCCH
Siemens 2G TCH
Siemens 2G PDCH
Siemens 2G Abis
Congestion Counter
VS.RRC.Rej.ULCE.Cong+VS.RAB.FailEstabCS.ULCE.Cong+VS.RAB.FailEstabPS.ULCE.Cong
VS.RRC.Rej.DLCE.Cong+VS.RAB.FailEstabCS.DLCE.Cong+VS.RAB.FailEstabPS.DLCE.Cong
VS.RRC.Rej.ULPower.Cong+VS.RAB.FailEstabCS.ULPower.Cong+VS.RAB.FailEstabPS.ULPower.Cong
VS.RRC.Rej.DLPower.Cong+VS.RAB.FailEstabCS.DLPower.Cong+VS.RAB.FailEstabPS.DLPower.Cong
VS.RRC.Rej.ULIUBBand.Cong+VS.RAB.FailEstabCS.ULIUBBand.Cong+VS.RAB.FailEstabPS.ULIUBBand.Cong
VS.RRC.Rej.DLIUBBand.Cong+VS.RAB.FailEstabCS.DLIUBBand.Cong+VS.RAB.FailEstabPS.DLIUBBand.Cong
VS.RRC.Rej.Code.Cong+VS.RAB.FailEstabCS.Code.Cong+VS.RAB.FailEstabPS.Code.Cong
rrc_conn_stp_fail_bts+rab_stp_fail_cs_voice_bts+rab_stp_fail_ps_strea_bts+rab_stp_fail_ps_inter_frozbs+rab_stp_fail_ps_backg_frozbs+s
hs_dsch_str_1+setup_fail_bts_hs_dsch_bgr
rrc_conn_stp_fail_bts+rab_stp_fail_cs_voice_bts+rab_stp_fail_ps_strea_bts+rab_stp_fail_ps_inter_frozbs+rab_stp_fail_ps_backg_frozbs+s
hs_dsch_str_1+setup_fail_bts_hs_dsch_bgr
rrc_conn_stp_fail_ac+rab_stp_fail_cs_voice_ac+rab_stp_fail_ps_strea_ac +rab_stp_fail_ps_inter_ac+rab_stp_fail_ps_backg_ac
rrc_conn_stp_fail_iub_aal2+rab_stp_fail_cs_v_iub_aal2+setup_fail_iub_hs_total_str_1+setup_fail_iub_hs_total_int+setup_fail_iub_hs_tota
K3001:Failed SDCCH Seizures due to Busy SDCCH
K3011A:Failed TCH Seizures due to Busy TCH (Traffic Channel)
[A9003:Number of Failed Uplink GPRS TBF Establishments due to No Channel]

+[A9203:Number of Failed Uplink EGPRS TBF Establishments due to No Channel]+[A9103:Number of Failed Downlink GPRS TBF Establishmen
Channel]
+[A9303:Number of Failed Downlink EGPRS TBF Establishments due to No Channel]}
[R9394:Number of PDCH Application Failures due to no Convertable TCHs]+[R9395:Number of PDCH Application failures For CELL PDCH Rati
[R9346:Number of Dynamic PDCH Requests Without Application Attempts Because the Number of Activated PDCHs Reaches Board Specifica
[R9347:Number of Dynamic PDCH Requests Without Application Attempts Because No Abis Timeslot is Available for Use]
R9347:Number of Dynamic PDCH Requests Without Application Attempts Because No Abis Timeslot is Available for Use
100 * ([SDCCH_BUSY_ATT] - [TCH_SEIZ_DUE_SDCCH_CON])/[SDCCH_SEIZ_ATT])

100 * ([TCH_REQUESTS_CALL_ATTEMPT] - [SUCC_TCH_SEIZ_CALL_ATTEMPT])/[TCH_REQUESTS_CALL_ATTEMPT]
100 * ([NO_RADIO_RES_AVA_DL_TBF] + [NO_RADIO_RES_AVA_UL_TBF])/([NBR_OF_DL_TBF] + [NBR_OF_UL_TBF])
dl_tbfs_with_inadeq_edap_res + ul_tbfs_without_edap_res
ATSDCMBS / NATTSDPE
(ATCHSMBS_1 + ATCHSMBS_2) /(ATTCHSEI_1 +ATTCHSEI_2) --> excluding A-bis blocking
(ATCHSMBS_1 + ATCHSMBS_2 + ATCHSMBS_3 + ATCHSMBS_4) /(ATTCHSEI_1 +ATTCHSEI_2) --> including A-bis blocking
REJPDASS_1..37 / (NUACATCL_3 + NUACATCL_6)
ABISPSUP[7]/(ABISPSUP[6] + ABISPSUP[7])
Case 1st Action

CE Blocking/CE High Util Check trending of CE Availability
Iub Blocking/Iub High Util Physical Audit (involving TP analysis)
DL- Power Blocking/DL - Power High Util Physical Audit (involving TP analysis)
UL- Power Blocking Physical Audit (involving TP analysis)
Code Blocking Physical Audit (involving TP analysis)

2nd Action 3rd Action
Physical Audit (involving TP analysis) CE license and/or board upgrade
IuB VC Split Iub BW upgrade
Activate 40W, maintain existing PCPICH setting Increase PtxTarget, PtxMaxHSDPA
Increase PrxTarget, adjust
DeltaPrxMaxUp,DeltaPrxMaxDown
Decrease used MaxBitrateDLPSNRT (128 kbits/s, 64
kbits/s)
Type Blocking
SDCCH blocking & Non TCH Blocking
CS Blocking & Non PS blocking

TCH Blocking & Non SDCCH blocking
TCH Blocking & SDCCH blocking
PS Blocking ->due to no Convertable TCHs
PS Blocking & Non CS blocking PS Blocking->due to CELL PDCH Ratio Thresh
PS Blocking->due to Activated PDCHs Reaches

Board Specification
PS Blocking->Abis Timeslot is Available for Use
CS Blocking & PS blocking
2G/3G reselection ( traffic share)

First step
check channel availability rate & Abis transmission availiblity

rate,any intermittent rise TT (cause maybe due to Abis IP capacity
problem)

problem)

problem)

problem)

problem)

problem)
Second step
1.reduce MS MAX Retrans

2.Increase CRH (LAC border area)
3.Add fix SDCCCH channel
4.RACH Busy Threshold
5.ReduceCS RACH Min. Access Level
6.SDDYN->Yes (SDCCH Dynamic Allocation Allowed)
1.Enable TCH Rate Adjust Allow

2.Reduce TCHBUSYTHRES
&AMRTCHHPRIORALLOW&AMRTCHHPRIORLOAD
3.Change SDCCH &PDCH to TCH channel
4.Enable load handover
5.PT & CRO
6.Counter A312F,TDM-> Reduce idle TS & upgrade Abis;IP
mode upgrade Abis
1.same as upper reduce SDCCH & TCH blocking

2.PT &C CRO
3.Power adjust ( increase adjcent cells power type if
possble)
4.upgrade TRX
1.Add fix PDCH channel

2.UPDYNCHNTRANLEV & DWNDYNCHNTRANLEV(20-
>70,20->80)
3.DYNCHFREETM(20->15)
1.Increase MAX PDCH rate threshold

2.PDCHUPLEV & PDCHDWNLEV(20->70,20->80)
3.DYNCHFREETM(15->10)
DSP Re-balance
Abis upgrade (IP mode increase BW)
1.Upgrade TRX or Abis transmission capacity

2.If upgrade limit,change PDCH to TCH (CS high priority)
3.Load sharing to 3G, FDD Qmin (7-->6[max -14db]) &
SSEARCHRAT (2-->0)
1.Inter-RAT Cell Reselection Enable(IRAT reseclection)

2.Qsearch C Initial(seach 3G in Idle mode)
3.Qsearch I(7=always seach 3G)
4.FDD Qmin (3G candidate cells EC/NO threshold)
5.FDD Qmin Offset(candidate cells EC/NO offset)
Type Blocking
SDCCH blocking & Non TCH Blocking
CS Blocking & Non PS blocking
TCH Blocking & Non SDCCH blocking
TCH Blocking & SDCCH blocking
PS Blocking, TCH not Blocking
PS Blocking & Non CS blocking
PS Blocking (Abis)
Analyze
check channel availability rate (TCH Availability) & Transmission

performance, any intermittent or not (Alarm). If all Ok then do the
action coloum

action coloum

action coloum

action coloum

action coloum
Action
1.Reduce CRH (Cell Reselect Hysteresis = HYS) if site in the LAC

border area and increase CRH for the NR cell in another LAC
2.Reduce CRO (Cell Resellect Offset =REO) or make negative
value by set Penalty Time (PET) to 640s
3.Add fix SDCCCH channel
1. increase (btsSpLoadDepTchRateLower = FRL) &

(btsSpLoadDepTchRateUpper=FRU) maximum value is 90
2. Increase (amrSegLoadDepTchRateLower = AFRL) &
(amrSegLoadDepTchRateUpper = AFRU)
3. Change SDCCH &PDCH to TCH channel
4. Reduce hoMarginPbgt from blocking cell and increase
hoMarginPbgt to NR cell that is no blocking
1. same as upper reduce SDCCH & TCH blocking

2. Change PDCH to TCH if PDCH not blocking or less
3.upgrade TRX
1.Add Dedicated GPRS Capactity (CDED) by increase the number

2. Add Default GPRS Capacity (CDEF) byt increase the number
(Dynamic)
1. Reduce egprsInitMcsAckMode (MCA) &

egprsInitMcsUnAckMode (MCU)
Type Blocking First step
check channel availability rate & Abis

SDCCH blocking & Non transmission availiblity rate,any
TCH Blocking intermittent rise TT (cause maybe due to
Abis problem)
CS Blocking & Non PS blocking check channel availability rate & Abis
TCH Blocking & Non transmission availiblity rate,any
SDCCH blocking intermittent rise TT (cause maybe due to
Abis problem)

TCH Blocking & SDCCH transmission availiblity rate,any
blocking intermittent rise TT (cause maybe due to
Abis problem)

PS Blocking -> due to no transmission availiblity rate,any
PDCH resource intermittent rise TT (cause maybe due to
Abis problem)
PS Blocking & Non CS blocking check channel availability rate & Abis
PS Blocking -> due to PDT transmission availiblity rate,any
resource intermittent rise TT (cause maybe due to
Abis problem)
PS Blocking-> no Abis
Timeslot is Available

transmission availiblity rate,any
CS Blocking & PS blocking intermittent rise TT (cause maybe due to
Abis IP capacity problem)
2G/3G reselection ( traffic share)

Second step
1. Reduce SDCCHCONGTH (70 --> 50/40)

2. Increase CELLRESH (LAC border area)
3. Change TCH_HLF timeslot to TCHSD timeslot
4. Add fix SDCCH timeslot
4. Reduce RACHBT (109 --> 106)
1. Reduce HRACCT1 and HRACTAMRACT1

2. Reduce GPDPDTCH
3. Reduce GMANPRESPRM & EMANPRESPRM
4. Increase SDCCHCONGTH (max: 100)
1. Same as upper reduce SDCCH & TCH blocking

2. Increase PWRRED to 2
3. Upgrade TRX
1. Increase GMANPRESPRM & EMANPRESPRM

2. Increase GPDPDTCH
Rebalancing PRPTPGID
1. Change GASTRABISTH to 60-70-40-50

2. Add SUBTSLB on A-bis
1.Upgrade TRX or Abis transmission capacity

2.If upgrade limit,change PDCH to TCH (CS high priority)
3.Load sharing to 3G, FDD Qmin (7-->6[max -14db]) & SSEARCHRAT
(2-->0)
1.Inter-RAT Cell Reselection Enable(IRAT reseclection)

2.Qsearch C Initial(seach 3G in Idle mode)
3.Qsearch I(7=always seach 3G)
4.FDD Qmin (3G candidate cells EC/NO threshold)
5.FDD Qmin Offset(candidate cells EC/NO offset)
No Equipment Tech Parameter Name Category
1 Huawei 3G NBMULCACALGOSELSWITCH Power Blocking
2 Huawei 3G PILOTPO, DLDPCHSF256PILOTBIT Power Blocking
3 Huawei 3G MAPSWITCH_MAP_HSUPA_TTI_2MS_SWITCH CE Blocking
4 Huawei 3G N300 SPU Load
5 Huawei 3G BeHsupa2msTTIratethd RTWP
6 Huawei 3G CSRABCacOptSwitch Overall 3G Radio Blocking
7 Huawei 3G PsInactTmrForPreFstDrm SPU Load
8 Huawei 3G CQIFbCk, CQIFbCkforSHO RTWP
9 Huawei 3G ULTOTALEQUSERNUM Power Blocking
10 Huawei 3G HSPDSCHCODENUM Code Blocking
11 Huawei 3G DLHOCECODERESVSF Code Blocking
12 Huawei 3G HoASUtmr Overall 3G Radio Blocking
13 Huawei 3G RLMAXDLPWR & RLMINDLPWR RTWP
14 Huawei 3G SSEARCHRAT Overall 3G Radio Blocking
15 Huawei 3G EAGCHCODENUM HSDPA Throughput
16 Huawei 3G UlOlcTrigThd Power Blocking
17 Huawei 3G SMPAGECTHD & SMPAGERTHD Paging

18 Huawei 3G TrigRatioforUlRTWP RTWP
19 Huawei 3G RLMAXDLPWR & RLMINDLPWR Power Blocking
20 Huawei 3G ULHOCERESVSF& ULRRCCERESVSF Code Blocking
21 Huawei 3G DLLDRTRIGTHD Overall 3G Radio Blocking
22 Huawei 3G RSCALLOCM HSDPA Throughput
23 Huawei 3G DLCONVAMRTHD Power Blocking
24 Huawei 3G DLCONVNONAMRTHD Power Blocking
25 Huawei 3G DLOTHERTHD Power Blocking
26 Huawei 3G DLHOTHD Power Blocking
27 Huawei 3G DLCELLTOTALTHD Power Blocking
28 Huawei 3G DLLDRFIRSTACTION Power/Code Blocking
29 Huawei 3G DLLDRSECONDACTION Power/Code Blocking
30 Huawei 3G DLLDRTHIRDACTION Power/Code Blocking
31 Huawei 3G DLLDRFOURTHACTION Power/Code Blocking
32 Huawei 3G DLLDRFIFTHACTION Power/Code Blocking

33 Huawei 3G SLOTFORMAT FACH Congestion
34 Huawei 3G DLLDRRELTHD Overall 3G Radio Blocking
35 Huawei 3G MAXTARGETULLOADFACTOR HSUPA Throughput

36 Huawei 3G HSPAPOWER HSDPA Throughput
37 Huawei 3G SM HSDPA Throughput
38 Huawei 2G MAXPDCHRATE PDCH Blocking
39 Huawei 2G PDCHUPLEV PDCH Blocking
40 Huawei 2G PDCHDWNLEV PDCH Blocking
41 Huawei 2G UPDYNCHNTRANLEV PDCH Blocking
42 Huawei 2G DWNDYNCHNTRANLEV PDCH Blocking
43 Huawei 2G PSServiceBusyThreshold PDCH Blocking
44 Huawei 2G IDLESDTHRES SDCCH Blocking
45 Huawei 2G TCHBUSYTHRES TCH Blocking
46 Huawei 2G AMRTCHHPRIORALLOW TCH Blocking
47 Huawei 2G AMRTCHHPRIORLOAD TCH Blocking
48 Siemens 2G SDCCHCONGTH SDCCH Blocking
49 Siemens 2G HRACTT1, HRAMRHRACT1 TCH Blocking
50 Siemens 2G GPDPDTCHA PDCH Blocking
51 Siemens 2G GASTRABISTH Abis Blocking
52 Siemens 2G CHTYPE=SDCCH (from TCH) SDCCH Blocking
53 Siemens 2G CHTYPE=TCH (from SDCCH) SDCCH Blocking
54 Siemens 2G CHTYPE=CCCH (from TCH) SDCCH Blocking
55 Siemens 2G INIMCSDL PCU Load

56 Nokia 2G btsSpLoadDepTchRateLower (FRL) TCH Blocking
57 Nokia 2G btsSpLoadDepTchRateUpper (FRU) TCH Blocking
58 Nokia 2G amrSegLoadDepTchRateLower (AFRL) TCH Blocking
59 Nokia 2G amrSegLoadDepTchRateUpper (AFRU) TCH Blocking
60 Nokia 2G hoMarginPbgt TCH Blocking
61 Nokia 2G dedicatedGPRSCapacity (CDED) PDCH Blocking
62 Nokia 2G defaultGPRSCapacity (CDEF) PDCH Blocking
63 Nokia 2G egprsInitMcsAckMode (MCA) PDCH Blocking
64 Nokia 2G egprsInitMcsUnAckMode (MCU) PDCH Blocking
Purpose Applicable Condition
When Cell having Low accessibility due UL Power
Disable uplink call admission control algorithm
Congestion >0.5%
Reduce DL Power Congestion & Increase HS When Cell having Low accessibility due DL Power
Throughput Congestion >0.5%
When Cell having Low accessibility due UL Power

Disable 2ms TTI for HSUPA service
Congestion >0.5%
reduce Maximum number of retransmissions of the

High SPU Load due traffic increase >70%
RRC CONNECTION REQUEST message.E.g from 3 to 1
increase Threshold of selecting TTI 2ms for HSUPA UL CE Congestion, UL Power Congestion >0.5%
When Cell having Low accessibility due CS RAB

Enable loose CAC algorithm for CS RAB
Congestion >0.5%
increase CELL-PCH inactivity timer for UEs enabled

High SPU Load due traffic increase >70%
with the Fast Dormancy feature
Reduce Uu Load & improve RTWP to increase CS
Cell having high DCR CS with High RTWP indication
Traffic
When Cell having Low accessibility due UL- Power

Increase ULTOTALEQUSERNUM (e.g from 160 to 180)
Blocking for Existing value is less than 200
When Cell having Low accessibility due Code

Reduce HSPDSCHMINCODENUM (e.g from 5 to 4)
Blocking >0.5%
Modify DLHOCECODERESVSF to lower SF (e.g from When Cell having Low accessibility due Code
SF32 to SF 64) Blocking >0.5%
when many cells is having High Drop CS due to
Increase HoASUtmr
ASU/SRB Reset
when cell is having High Drop CS due to RL/No Reply

Increase RLMAXDLPWR & RLMINDLPWR (eg: 0/-150 to
& Power Blocking is low (suggest on cell with high
20/-130)
power Capacity & DL Power cong <0.5%)
when many cells is having High Drop CS due to

time being increase SSEARCHRAT >0
interference, DCR >1%
When HSUPA Throughput is low, suitable to optimize
increase EAGCHCODENUM, E.g from 1 to 2
adhoc site such as VIP site
Cell with High UL Power Cong (>0.5%)after

increase UlOlcTrigThd to 100 (while still in
Algorithm_OFF . To implement many cell need
ALGORITHM_OFF)
consider Processor Load is low to Medium (<70%)
Increase SMS Threshold e.g from

RNC High Paging deletion
SMPAGECTHD=85,SMPAGERTHD=75 to
(VS.Paging.FC.Disc.Num.CPUS)
SMPAGECTHD=95,SMPAGERTHD=85;
Increase TrigRatiororUlRTWP e.g 75 to 90 Cell with High RTWP and no congestion issue
decrease RLPower : RLMAXDLPWR,RLMINDLPWR (eg. When Cell having Low accessibility due High DL
50,-100 to 0,-150 ) Power Cong >0.5%
Set lower SF on ULHOCERESVSF& ULRRCCERESVSF e.g When Cell having Low accessibility due
SF16->SF32 RRC.Rej.ULCE.Cong
Cell with High DL Power Blocking .To implement

set DLLDRTRIGTHD to lower value many cell need consider Processor Load is low to
Medium
Change NodeB Resource allocation mode to Power When HSDPA Throughput is low, suitable to optimize
Code Balance adhoc site such as VIP site
When Cell having Low accessibility due High DL

Increase DL Power threshold for AMR
Power Cong >0.5%
Increase DL Power threshold for Non-AMR
Power Cong >0.5%
Increase DL Power threshold for Other
Power Cong >0.5%
Increase DL Power threshold for HO
Power Cong >0.5%
Increase DL Power Total threshold
Power Cong >0.5%
Rearange LDR Sequence
Power Cong/Code Cong >0.5%
Change FACH SlotFormat to expand FACH Bandwidth
When Cell having High FACH Congestion
using Higher format ex : from D8 to D10
Cell with High DL Power Blocking .To implement

set DLLDRTRIGTHD to lower value many cell need consider Processor Load is low to
Medium
Increase UL Load Factor of HSUPA Low Throughput in Cell Level
Increase HSDPA Power Low Throughput in Cell Level
Change MACHSPARA SM to MAXCI Low Throughput in Cell Level
Reduce PDCH blocking PDCH blocking due to no Convertable TCHs
Reduce TBF congestion PDCH blocking due to CELL PDCH Ratio Thresh
Reduce TBF congestion PDCH blocking due to CELL PDCH Ratio Thresh
Reduce TBF congestion PDCH blocking due to no Convertable TCHs
Reduce SDCCH blocking SDCCH blocking & Non TCH Blocking
Reduce SDCCH & TCH blocking TCH blocking & SDCCH, TCH blocking
Reduce SDCCH Blocking SDCCH Utilization > 80%
Reduce TCH Blocking TCH Blocking Rate > 1%
Increase/decrease dynamic PDCH allocation to reduce PDCH Blocking Rate > 1%
PDCH Blocking
Reduce A-bis pool blocking in order to improve PDASR Abis Pool Loss Rate > 0.5%
Reduce SDCCH Blocking with change Channel Type SDCCH Blocking > 0.5%
from TCH to SDCCH
Reduce TCH Blocking with change Channel Type from TCH Blocking > 1% AND SDCCH Utilization < 50%
SDCCH to TCH
Resolve AGCH and PCH overload with change Channel PCH load + AGCH load > 80%
Type from TCH to CCCH
To reduce initial Coding Scheme PCU Load > 90% and PDCH Blocking Rate > 1%
Reduce PDCH Blocking PDCH Blocking Rate > 1%
Cons
Noise will increase without admission control
Algorithm, might increase RTWP/degrade EcNo
CS/PS CDR may increase on RNC has the poor
coverage, or the coverage radius is big, use higher
PILOTPO=8 on this condition
HSUPA Throughput will degraded with only 10 ms TTI
lower value UE experiences difficulty accessing the

network when the Uu interface quality is poor or the
system is overloaded
user perceive will degraded with higher threshold to
HO from 10ms to 2ms TTI
PS service setup success rate and the cell capacity for
PS services will decrease in the case of cell resource
congestion
PS Total Traffic will decrease & RRC SR will statistically
degrade due less attempt
If value is larger, the cell capacity for uplink equivalent

user number (ENU) is large and more users will be
admitted
HSDPA Throughput will degraded with lower PDSCH
Code
degrading bitrate might occur while HO or RRC
SHO Overhead will be degraded
DL Power Cong will increase
Traffic aggresively to 2G
higher value will waste downlink codes
impact to processor load if too many cells

implemented
increase CPU Load

Might impact to capacity since UE QOS will trigger to
TTI 2ms in case of overload
Fail due Uu No reply/RL fail will increase
degrading bitrate might occur while HO or RRC

implemented
SET
MACHSPARA:LOCELL=4,RSCALLOCM=POWERCODE_B
AL;
Noise will increase, might increase RTWP

implemented
Throughput
Throughput
Throughput
Throughput
Throughput
Throughput
TCH utilization
quality
quality
quality
Possible increase TCH Blocking
Degraded voice quality and SQI
Low throughput
Possible increase SDCCH Blocking
Low throughput
Command Sample (Optional)
MOD UCELLALGOSWITCH:CELLID=xxxxx,NBMULCACALGOSELSWITCH=ALGORITHM
SET UFRC:PILOTPO=4,DLDPCHSF256PILOTBIT=D2;
SET UCORRMALGOSWITCH:MAPSWITCH=MAP_HSUPA_TTI_2MS_SWITCH-0
SET UIDLEMODETIMER:N300=1;
SET UFRC:BEHSUPA2MSTTIRATETHS=D1024;
MOD UCELLALGOSWITCH:CELLID=XXXXX,CSRABCACOPTSWITCH=ON;
SET UPSINACTTIMER:PSINACTTMRFORPREFSTDRM=900,
MOD UCELLHSDPCCH:CELLID=XXXXX,CQIFBCK=D20,CQIFBCKFORSHO=D20
MOD UCELLCAC:CELLID=XXXXX,ULTOTALEQUSERNUM=180,
MOD UCELLHSDPA:CELLID=XXXXX,ALLOCCODEMODE=Manual,HSPDSCHCODENU
MOD UCELLCAC:CELLID=31890,DLHOCECODERESVSF=SF64;
SET USTATETIMER:HOASUTMR=8000;
MOD UCELLRLPWR:RLMAXDLPWR=20, RLMINDLPWR=-130
ADD UCELLSELRESEL:CELLID=XXXXX,SSEARCHRAT=0;
ADD UCELLHSUPA:CELLID=31890,EAGCHCODENUM=2;
ADD UCELLLDM:CELLID=31890,ULOLCTRIGTHD=100;
SET FCCPUTHD:BRDCLASS=XPU,SMPAGECTHD=95,SMPAGERTHD=85;
MOD UCELLLDM:CELLID=XXXXX,TRIGRATIOFORULRTWP=73;
MOD UCELLRLPWR:RLMAXDLPWR=0, RLMINDLPWR=-150
ADD UCELLCAC:CELLID=31890,ULHOCERESVSF=SF32;
ADD UCELLLDM:CELLID=31890,DLLDRTRIGTHD=80;
SET MACHSPARA:LOCELL=4,RSCALLOCM=POWERCODE_BAL;
MOD UCELLCAC: CELLID=1, DLCONVAMRTHD=90;
MOD UCELLCAC: CELLID=1, DLCONVNONAMRTHD=90;
MOD UCELLCAC: CELLID=1, DLOTHERTHD=80;
MOD UCELLCAC: CELLID=1, DLHOTHD=95;
MOD UCELLCAC: CELLID=1, DLCELLTOTALTHD=95;
MOD UCELLLDR: CELLID=1, DLLDRFIRSTACTION=CodeAdj;
MOD UCELLLDR: CELLID=1, DLLDRSECONDACTION=InterFreqLDHO;
MOD UCELLLDR: CELLID=1, DLLDRTHIRDACTION=BERateRed;
MOD UCELLLDR: CELLID=1, DLLDRFOURTHACTION=CSInterRatShouldNotLDH
MOD UCELLLDR: CELLID=1, DLLDRFIFTHACTION=PSInterRatShouldNotLDHO

DEA UCELL: CELLID=30706;
DEA USCCPCH: CELLID=30706, PHYCHID=9;
RMV UFACHLOCH: CELLID=30706, TRCHID=4;

RMV UFACHDYNTFS: CELLID=30706, TRCHID=4, RLCSIZE=168;
RMV UFACHDYNTFS: CELLID=30706, TRCHID=5, RLCSIZE=360;
RMV UFACH: CELLID=30706, TRCHID=4;
RMV UFACH: CELLID=30706, TRCHID=5;
RMV USCCPCH: CELLID=30706, PHYCHID=9;
ADD USCCPCHBASIC: CELLID=30706, PHYCHID=9, SCCPCHOFFSET=100, SCRAMBCODE=0, SLOTFORMAT=

ADD USCCPCHTFC: CELLID=30706, PHYCHID=9, CTFC=0;
ADD UFACH: CELLID=30706, PHYCHID=9, TRCHID=4, RATEMATCHINGATTR=220, TOAWS=35, TOAWE=10, MAXFACHPOW
ADD UFACH: CELLID=30706, PHYCHID=9, TRCHID=5, RATEMATCHINGATTR=130, TOAWS=35, TOAWE=10, MAXCMCHP
CHCODINGTYPE=TURBO;
ADD UFACHDYNTFS:CELLID=30706, TRCHID=4, RLCSIZE=168, TFSNUMBER=D3, TBNUMBER1=0, TBNUM
ADD UFACHDYNTFS:CELLID=30706, TRCHID=5, RLCSIZE=360, TFSNUMBER=D3, TBNUMBER1=0, TBNUM
ADD UFACHLOCH: CELLID=30706, TRCHID=4;
ACT USCCPCH: CELLID=30706, PHYCHID=9;
ACT UCELL: CELLID=30706;
ADD UCELLLDM:CELLID=31890,DLLDRTRIGTHD=80;
MOD UCELLHSUPA: CellId=1, MAXTARGETULLOADFACTOR=90;

MOD UCELLHSDPA: CellId=1, HspaPower=0;
SET MACHSPARA:LOCELL=1,SM=MAXCI;
SET GCELLPSCHM: IDTYPE=BYID, CELLID=0, MAXPDCHRATE=80;
SET GCELLPSCHM:IDTYPE=BYID,CELLID=1,PDCHUPLEV=70;
SET GCELLPSCHM:IDTYPE=BYID,CELLID=1,PDCHDWNLEV=160;
SET GCELLPSCHM:IDTYPE=BYID,CELLID=1,UPDYNCHNTRANLEV=70;
SET GCELLPSCHM:IDTYPE=BYID,CELLID=1,DWNDYNCHNTRANLEV=80;
SET GCELLPSCHM:IDTYPE=BYID,CELLID=1,PSSERVICEBUSYTHRESHOLD=40;
SET GCELLCHMGBASIC:IDTYPE=BYID,CELLID=1,IDLESDTHRES=8;
SET GCELLCHMGAD:IDTYPE=BYID,CELLID=1,TCHBUSYTHRES=2;
SET GCELLCHMGAD:IDTYPE=BYID,CELLID=1,AMRTCHHPRIORALLOW=ON,AMRTCHHPRI
SET GCELLCHMGAD:IDTYPE=BYID,CELLID=1,AMRTCHHPRIORALLOW=ON,AMRTCHHPRI
Equipment Tech Parameter Name Category
Huawei 3G BeHsupa2msTTIratethd RTWP
Huawei 3G CQIFbCk, CQIFbCkforSHO RTWP
Huawei 3G RLMAXDLPWR & RLMINDLPWR RTWP
Huawei 3G TrigRatioforUlRTWP RTWP

Purpose Applicable Condition
increase Threshold of selecting TTI 2ms for HSUPA UL CE Congestion, UL Power Congestion >0.5%
Reduce Uu Load & improve RTWP to increase CS Traffic Cell having high DCR CS with High RTWP indication
when cell is having High Drop CS due to RL/No Reply &

Increase RLMAXDLPWR & RLMINDLPWR (eg: 0/-150 to Power Blocking is low (suggest on cell with high power
20/-130) Capacity & DL Power cong <0.5%)
Increase TrigRatiororUlRTWP e.g 75 to 90 Cell with High RTWP and no congestion issue
Cons Command Sample (Optional)
user perceive will degraded with higher threshold to HO SET UFRC:BEHSUPA2MSTTIRATETHS=D1024;
from 10ms to 2ms TTI
MOD
UCELLHSDPCCH:CELLID=XXXXX,CQIFBCK=D20,CQIFBCKFO
RSHO=D20
DL Power Cong will increase MOD UCELLRLPWR:RLMAXDLPWR=20, RLMINDLPWR=-

130
Might impact to capacity since UE QOS will trigger to TTI MOD

2ms in case of overload UCELLLDM:CELLID=XXXXX,TRIGRATIOFORULRTWP=73;
Equipment Tech Parameter Name Category Purpose
Huawei 3G EAGCHCODENUM HSDPA Throughput increase EAGCHCODENUM, E.g from 1 to 2
Huawei 3G RSCALLOCM HSDPA Throughput Change NodeB Resource allocation mode to Power Code Balance
Huawei 3G MAXTARGETULLOADFACTOR HSUPA Throughput Increase UL Load Factor of HSUPA
Huawei 3G HSPAPOWER HSDPA Throughput Increase HSDPA Power
Huawei 3G SM HSDPA Throughput Change MACHSPARA SM to MAXCI

Applicable Condition Cons Command Sample (Optional)
When HSUPA Throughput is low, suitable to higher value will waste downlink codes ADD UCELLHSUPA:CELLID=31890,EAGCHCODENUM=2;
optimize adhoc site such as VIP site
SET
When HSDPA Throughput is low, suitable to MACHSPARA:LOCELL=4,RSCALLOCM=POW SET MACHSPARA:LOCELL=4,RSCALLOCM=POWERCODE_BAL;
optimize adhoc site such as VIP site ERCODE_BAL;
Low Throughput in Cell Level MOD UCELLHSUPA: CellId=1, MAXTARGETULLOADFACTOR=90;
Low Throughput in Cell Level MOD UCELLHSDPA: CellId=1, HspaPower=0;
Low Throughput in Cell Level SET MACHSPARA:LOCELL=1,SM=MAXCI;

RNO Analysis Mate V1 01

Cargado por

Información del documento

Título original

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

RNO Analysis Mate V1 01

Cargado por

Copyright:

Formatos disponibles

RNO Analysis Mate

Developed By: Manik Kapoor

Iub Blocking/Iub High Util Verify Iub BW setting in Node-B and in

DL- Power Blocking/DL - Power High Util Physical Audit

UL- Power Blocking Physical Audit

Code Blocking Physical Audit

Physical Audit CE license and/or board upgrade

Physical Audit Iub BW upgrade

Modify DL CAC parameters set to

Increase ULTOTALEQUSERNUM (e.g Turn-off

Modify LDR threshold. Sets involved :

Modify FTI to reduce Active Factor. Sets

Reduce HSSCCHCODENUM (e.g from 4

Basic Channel Element Concepts

CE Sharing in a Resource Group

NodeB CE Capacity Specifications

Rules for Calculating CE Consumption

Common Channels CE Consumption

HSDPA Channels CE Consumption

R99 Service CE Consumption

HSUPA Service CE Consumption

CE Consumption of 4-Way Receive Diversity

Change of best frequency

Transport Channel Traffic Volume becomes larger than an absolute threshold

A predefined number of bad CRCs is exceeded

The UE position changes more than an absolute threshold

signal-to-noise ratio (SNR)

Note 3 : I used the following formula explained in Code Rate section.

CQI is carried by PUCCH or PUSCH depending on the situation as follows.

Carried by PUCCH : Periodic CQI

< Two Important CQI Table >

This table is used in following case :

Handover and Related Parameters

Serial Parameters of Cell Selection and Reselection

Frequency Hopping Parameters

Case 4: Call drop caused by clock problem

Vendor Tech Resource Type

[A9003:Number of Failed Uplink GPRS TBF Establishments due to No Channel]

100 * ([SDCCH_BUSY_ATT] - [TCH_SEIZ_DUE_SDCCH_CON])/[SDCCH_SEIZ_ATT])

Case 1st Action

UL- Power Blocking Physical Audit (involving TP analysis)

Code Blocking Physical Audit (involving TP analysis)

SDCCH blocking & Non TCH Blocking

CS Blocking & Non PS blocking

TCH Blocking & SDCCH blocking

PS Blocking ->due to no Convertable TCHs

PS Blocking & Non CS blocking PS Blocking->due to CELL PDCH Ratio Thresh

PS Blocking->due to Activated PDCHs Reaches

PS Blocking->Abis Timeslot is Available for Use

CS Blocking & PS blocking

2G/3G reselection ( traffic share)

check channel availability rate & Abis transmission availiblity

check channel availability rate & Abis transmission availiblity

check channel availability rate & Abis transmission availiblity

check channel availability rate & Abis transmission availiblity

check channel availability rate & Abis transmission availiblity

check channel availability rate & Abis transmission availiblity

1.reduce MS MAX Retrans

1.Enable TCH Rate Adjust Allow

1.same as upper reduce SDCCH & TCH blocking

1.Add fix PDCH channel

1.Increase MAX PDCH rate threshold

Abis upgrade (IP mode increase BW)