Académique Documents
Professionnel Documents
Culture Documents
Optimization
Network Deployment Steps
High level PM data analysis and assessment
Yes
Weekly KPI
No Mapinfo
(RNC) Mataching failure
<X%? distribution into
network topology Solution Proposal
Yes
Channel RNC
Iub
element processing
transmission
allocation load
Number of
users
Principles of traffic monitoring -
bottlenecks
WBTS RNC
UE
IuCS Interface
User
User Plane
Plane
SS7 (RANAP)
Air Interface WSP Iub Interface
Resource Throughput
CNBAP IuPS Interface
PRACH Connectivity
FACH-c&u DNBAP
PCH Unit Load User Plane
AAL2 or IP SIG
Code User Plane DSP Usage SS7 (RANAP)
DCH
Capacity
User Plane
Iur Interface
Both interfaces and internal resources of
WCDMA network should be monitored
D-RNC
Principles of traffic monitoring - reactive /
Reactive monitoring proactive
Consider setup failure (already discussed in chapter 2)
Daily BH analysis needed
Proactive monitoring
Consider amount of traffic
Weekly analysis enough
Traffic Monitoring
Principles
Transmitted carrier power
Node B reporting
Total DL power
R99 power
HSDPA power
Received total wideband power
Code tree allocation
Channel element allocation
Iub transmission
RNC processing load
Number of users
Node B reporting
Node B informs RNC about air interface load by the following messages
Common NBAP radio resource indication
Transmitted carrier power
Total power R99 + HSDPA
R99 power
Received total wideband power
Total power R99 + HSUPA
HSUPA power (calculated by Node B, not directly measured)
Dedicated NBAP measurement report
Power of each dedicated radio link
C - NBAP
IuB D - NBAP
Node B RNC
Total DL power - optimization flow
High total DL
power
The definition of the load target depends on the presence of HSDPA users
No HSDPA user present static load target PtxTarget
At least one HSDPA user present dynamic load target PtxTargetPS
HSPA power
HSPA power includes
HS-PDSCH
All HS-SCCH
All HSUPA DL signaling channels (E-AGCH, E-RGCH, E-HICH)
HSDPA power - dynamic share with R99
DL power shared dynamically between R99 and HSDPA
Realized by dynamic load target for NRT R99 traffic PtxTargetPS
For RT R99 traffic still static load target PtxTarget
1) HSDPA congestion
Too much total DL power present in cell
PtxTotal PtxHighHSDPAPwr
PtxHighHSDPAPwr defines overload threshold for HSDPA cell (default 41 dBm)
2) DCH congestion
Too much R99 power present in cell
PtxMax 43 dBm
PtxHighHSDPAPwr
-10..50; 0.1; 41 dBm
PtxTotal
PtxTargetPSMax
-10..50; 0.1; 40 dBm
PtxTargetPS PtxTargetPSMin
-10..50; 0.1; 36 dBm
Optimum
load target PtxNonHSDPA PtxNRT
PtxNC
HSDPA power - dynamic share with R99
DCH Congestion
DCH power congestion, if If actual load target PtxTargetPS < optimum load target
PtxNonHSDPA PtxTargetPS - 1dB Increase PtxTargetPS by PtxTargetPSStepUp (default 1 dB)
PtxMax 43 dBm
PtxHighHSDPAPwr
PtxTotal
PtxTargetPSMax
PtxTargetPS
PtxTargetPSMin
Optimum
load target PtxNonHSDPA PtxNRT
PtxNC
RTWP sources
High adjacent cell Low adjacent cell
interference interference
i-factor
SF=8
SF=16
SF=32
SF=64
SF=128
R99 code allocation - blocking
Practical example single cell
Blocking per SF per hour
Blocking rate
for SF8
Total blocking rate
SF=1
SF=2
SF=4
SF=8
SF=16
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
. .
Examples
00000 00000 100000 = always 5 codes reserved (default)
11010 10100 100000 = number of reserved codes adjustable (5, 8, 10, 12, 14 or 15 codes, recommended)
RNC checks periodically, whether more codes can be reserved for HSDPA
Requirements for upgrade
Free adjacent codes to go to next higher level defined by HSPDSCHCodeSet
After upgrade still enough codes with SF128 available for R99 (at least HSPDSCHMarginSF128,
default = 8)
Upgrade to 15 codes possible only with HSPDSCHMarginSF128 = 0
HSDPA code allocation - dynamic share with R99
Downgrade due to NRT R99 traffic
SF=1
SF=2
SF=4
SF=8
SF=16
14 HS-PDSCH codes
SF=32
Codes for common
SF=64 channels in the cell Codes for associated DCHs
and non-HSDPA users
SF=128
E-RGCH/E-HICH (128)
High code congestion - optimization flow
High code
congestion
Still high
congestion
Service CE
SRB / voice / 16 K data 1
32 K data 2
64 K data 4
128 K data 4
256 K data 9
384 K data 12
R99 dimensioning
Less CE needed for DCH of 256 K and 384 K
All other rules remain unchanged
Service CE
SRB / voice / 16 K data 1
32 K data 2
64 K data 4
128 K data 4
256 K data 6
384 K data 8
High CE occupation - optimization flow
High CE
occupation
Many
Many DCH of High SHO
associated
low activity overhead
DCH
Configured bandwidth
Solution
After the patch is installed for the RNC, almost all the call drops with the cause being Other have disappeared
and the PS call drop rate is obviously lower, as shown in the following table. The problem is thus solved.
Note: You can get the table on the right via custom report or Performance Query of Nastar.
Traffic Monitoring
Principles
Transmitted carrier power
Received total wideband power
Code tree allocation
Channel element allocation
Iub transmission
RNC processing load
Number of users
Number of users - licenses
R99
No license for specific number of users per cell required
New user allocated, as long all types of RAN resources available
HSPA
License for specific number of users per cell required
The following levels are available
16 users
48 users
64 users
72 users
If maximum number of users present, new user rejected, even if all
types of RAN resources still available
Call setup - phases
RRC and RAB RRC connection setup
RAN resources reserved for
signaling connection between UE
and RNC
Phase: Setup Access Active RRC access
Connection between UE and RRC
RRC active
UE has RRC connection
Active If dropped, also active RAB dropped
Success
Setup Access Complete RAB setup
Complete Complete Attempts to start call
Active
Access
RAB setup access
Release Connection between UE and core
RAB active phase
Attempts
Start TX/RX
RRC Connection
L1 Synchronisation
Access phase
NBAP Synchronization Indication Waiting for UE reply
Start TX/RX
RRC Connection Access
phase L1 Synchronisation
NBAP Synchronization Indication Waiting for UE reply
UE max Tx power
and
high DL BLER
Very bad RSCP
Case 3:
PS: Session Error due to Poor DL Coverage
Configuration & NO
Minor
Yes
Yes
Zero High # fails for
attempts?
a source?
Failure
WCEL
High #
Yes In out attempts for
Low used Adjs pairs? a source?
Yes Yes
No Adjs Minor
Filtering over attempts must be taken into count that: Filtering over failure in absolute terms it is
- statistical data must stabilized over time.
possible to find the major critical events
- traffic distribution is not considered and a double-check to localize the
event and DT feedback is required to understand if fenomena is traffic
driven or cell dependent
Active Set Usage
Filtering criteria:
Major
- High number of failures for a defined out-going adjs (failure ADJS)
- high number of fail for a defined source (failure WCEL)
Minor
- high number of attempts in-comig and out-going for a defined pair with occasional failure
(ping-pong)
Filtering action are required to find bi-lateral corrispondence
- very low number of attempt with failure (low used adjs)
- zero number of attempt for declared adjs stabilized value (no adjs)
- high number of attempts with occsional failure for an out-going adjs (unbalanced ADJS)
Either in-coming or out-going condition is sufficient
- high number of attempts with occsional failure for a defined source (unbalanced WCEL)
Failure ADJS
Target_cell_A Target_cell_B Target_cell_C Target_cell_Z
Attempt Fail Attempt Fail Attempt Fail Attempt Fail
Source_cell_A 2 1 23 1 442 34 4 0
Source_cell_B 1 0 11 0 53 25 345 0
Source_cell_Z 322 54 15 0 2 0 12 0
Failure ADJS
Ec/Io
Reporting
P CPICH 1 Range
AdjsEcNoOffset
to modify measurement
reporting behaviour.
P CPICH 2 Effectively 'moves' cell
border (shrinks or
enlarges cell)
Enlarging Cell 3 by x dB
P CPICH 3
time
Reporting Reporting
Event 1B Event 1A
Failure ADJS Forbidding Neighbour Cell
Ec/Io
P CPICH 1
PCPICH3 is forbidden to
Reportin affect the reporting range as
g Range its quality is quite unstable.
AdjsDERR
P CPICH 2 to forbid a cell from reporting
range calculation in some
instances
P CPICH 3
Time
Failure WCEL
Target_cell_A Target_cell_B Target_cell_C Target_cell_Z
Attempt Fail Attempt Fail Attempt Fail Attempt Fail
Source_cell_A 2 1 23 15 442 34 124 23
Failure WCEL Source_cell_B 1 0 11 0 53 0 345 0
Source_cell_Z 322 1 15 0 2 0 12 0
Analyze Ec/No &BLER Most of the Target failure during the 1A or 1C event.
from DT & NWP coverage
plot considering inter-site
distance
The following gives the number of attempts per event
RT Services
KPI(1) = M1007C10 CELL ADD_REQUEST ON SHO FOR RT TRAFFIC
Yes
WCEL KPI(2) = M1007C12 CELL REPL_ REQUEST ON SHO FOR RT TRAFFIC NRT Services
Pollution/Interference
polluted/interfered?
KPI(1) = M1007C27 CELL ADD_ REQUEST ON SHO FOR NRT TRAFFIC
KPI(2) = M1007C29 CELL REPL_REQUEST ON SHO FOR NRT TRAFFIC
Analyze Ec/No from DT Once anlyzed the Ec/No, BLER, the coverage plot taking care to the
evaluation of intersite-distance, it is easy to understand if the WCEL is
interferered/Polluted
Yes If not, two KPIs allow to separate the dominant contribute among the 1A
KPI(1) ?
Tune 1A
and 1C.
Relaxing the parameters an improvement should be achieved
The failure rate for all the procedure can be estimated as well
ADD(REPL)_ FAIL_ONSHO _FOR_x / ADD(REPL)_REQ_ON_SHO_FOR_x +
Yes
ADD(REPL)_ FAIL_ONSHO _FOR_x
KPI(2) ? Tune 1C M1007C14 / M1007C12 + M1007C14
M1007C36 /M1007C11 + M1007C36
M1007C30 / M1007C27 + M1007C30
M1007C37 / M1007C28 + M1007C37
M1007C31 / M1007C29 + M1007C31
Failure WCEL - 1A
ActiveSetWeightingCoefficient
Ec/Io is used to weight either the
measurement result of the best active Strongest CPICH in AS: P CPICH 1
set cell (0) or the sum of measurement
results of all active set cells (<>0)
P CPICH 2 AdditionWindow
determines the relative
1A threshold used by the
UE to calculate the
reporting range of
event 1A. The threshold
is either relative to the
CPICH Ec/No
measurement result of
the best active set cell
(0), or to the sum of
active set measurement
P CPICH 3
results (<>0)
P CPICH 2
P CPICH 4
1C
ReplacementTime
Defines the period of time the monitored cell
must continuously stay within the reporting
range before the UE can send a Measurement
Report to the RNC in order to replace an active time
set cell with the monitored cell (event 1C).
ReplacementReportingInterval
If the RNC is not able to replace the active
cell with the monitored cell, the UE continues
reporting after the initial report by reverting to
periodical measurement reporting. The no
parameter Replacement Reporting Interval
determines the interval of periodical Measurement AS
measurement reports when such reporting is Report update?
triggered by the event 1C.
RNC
NO ADJS
Target_cell_A Target_cell_B Target_cell_C Target_cell_Z
Attempt Fail Attempt Fail Attempt Fail Attempt Fail
Source_cell_A 2 1 0 - 442 34 124 23
Source_cell_B 0 - 11 0 53 0 345 0
Source_cell_Z 322 1 15 0 2 0 12 0
No Adjs
Zero
attempts?
Repeat Analysis Comparing the ADJS plan provisioned into the
Yes network with the M1013 matrix, it is easy to find if one
declared ADJS is not used (not present in the list)
Statistic Statistic data must be stabilized before decide to
Stable? remove it and DT analysis can help n estimating the
amount of residual noise if down tilt is not possible
Yes
Remove ADJS
Low used ADJS
Target_cell_A Target_cell_B Target_cell_C Target_cell_Z
Attempt Fail Attempt Fail Attempt Fail Attempt Fail
Source_cell_A 2 1 25 4 442 34 124 23
Low used Adjs Source_cell_B 245 23 11 0 53 0 345 0
Source_cell_Z 322 1 3 1 2 1 123 20
Analyze DT
result and
NWP data
It is not difficult in live network to find some pair
working with very low
For low used ADJS has to be intended and ADJS that
Yes
Monitored Qual has few number of attemps in one day (e.g <3)
from DT
acceptable? with occasional failure.
The ADJS removal has to be considered as the last
option, after the quality has been monitored by drive
ADJ Offset
Alter. ADJS test result, considering the overall capability of the
present?
target to be recovered (e.g. inter-site distance, power
budget) and other options are available for that area.
Yes
Statistic data must be stabilized before decide to
Interference
remove it and DT analysis can help in estimating the
evaluation amount of residual noise if down tilt is not possible
Remove ADJS
Unbalanced ADJS
Ec/No offset
Unbalanced WCEL
Unbalanced WCEL
Yes
KPI(2) ? Tune 1C
Ping Pong
Down tilt
Target_cell_A Target_cell_B Target_cell_C Target_cell_Z
Attempt Fail Attempt Fail Attempt Fail Attempt Fail
DERR cell Source_cell_A 54 3 345 10 23 1 124 5
Yes
Source_cell_B 987 13 11 0 137 3
Source_cell_Z 32 2 45 2
Down tilt
possibile?
Ping-pong
No action
required
Yes In this particular case the high number
of attempt is concentrated in a pair
Analyze RSCP from DT & Attempt from
NWP coverage plot the same UE? From A >> B and from B >>A as in the
considering inter-site
distance
picture
As in the previous case could be an
indication of a problem and even in
case of the failure is not associated an
pollution One of them act
as polluter? evaluation is required to avoid to use a
lot signalling.
Yes Yes
Filtering Histeresys
using
Ec/NoOffset
on the pair
Ping Pong - Filtering
EcNoFilterCoefficient EcNoAveragingWindow
1. PSC Pollution
Too high reuse factor for the PSC. New PSC plan is required
2. DL Noise raise
ADJS signal strength out of usage window (will be never utilized by the UE)
A down tilt or power reduction is the solution evaluating all the side effects
3. Dominant site
A dominant site over-shooting the ADJ becoming congested
A down tilt or power reduction is the solution evaluating all the side effects
PSC Pollution
A confirm for the polluter of the first type can come from the counter
M1007C38-47 CELL SPECIFIC CPICH EC/NO - CLASS x
Pollution Criteria:
The M1007C38-47 gives an indication of Ec/No distribution value measured during event 1A .
Having the distribution highly unbalanced (normally centered on class 2, 3, 4) we have an
indication of a probable problem. For example unbalancing towards the scarce value of Ec/No
but continuing to add cells to AS could give an indication of pollution
High number
of class0-3?
Yes
High number of Isolated/unavailable
class>6? WCEL
Yes
Not Polluted WCEL
Polluted WCEL
DL Noise Raise
The NO ADJS and low used ADJS criteria before presented can give a confirm for a
pollution of this type.
After the statistical data are stabilized, making across-check with the provisioned ADJS
Plan the probable polluters are individuated.
This is obviously a cautelative estimation to be integrated and confirmed by drive test
results
Dominant site
Filtering the M1013 pairs for the recurrent target cell with associated occasional failure we
have an estimation of the probable polluters
For the polluters, originating failures a down tilt is required
Polluted Cell Criteria:
SHO over head can give a soft help in individuating cell where polluter/overshooting site
can be present or where unbalanced cell criteria could apply
GSM
GSM 3G 3G 3G
GSM
Value 0 1 6 7 8 9 10 14 15
dBm -98 -94 -74 Always -78 -74 -70 -54 Never
FDD_Qoffset and FDD_GPRS_Offset the non-GPRS/GPRS (respectively) capable UEs add this offset to the
RLA_C of the GSM cells. After that the UE compares the measured RSCP values of 3G cells with signal levels
of the GSM cells
Value 0 1 2 3 8 14 15
FDD_Qmin=0
RSCP (-20 dB)
Neighbour WCDMA Cell
Ec/N0
Minimum Quality Requirement for WCDMA
t
5 sec.
Cell Re-selection Example-Weaker WCDMA
GPRS case
RSCP/
RLA_C Ec/No
RLA_P
Cell re-selection to WCDMA
RSCP
FDD_Qmin
=-20 dB
4 3 2 1
WCDMA
CELL
Cell Reselection 3G -> 2G
No Yes
Rn (GSM) > Rs (WCDMA)
And
Rxlev (GSM) >QrxlevMin
Ranking is done using Criteria R, and the UE reselects to the cell with highest R-criteria. R-criteria is defined
as:
For serving cell: Rs = Qmeas,s + Qhysts
For neighboring cell Rn = Qmeas,n Qoffsetts,n
Qmeas is CPICH Ec/No for WCDMA cell and RxLev for GSM cell
How to avoid ping pong ?
When phone is camped on 3G, GSM measurements can start when CPICH Ec/Io of serving cell is below
Ssearch_RAT + QqualMin.
When phone is camped on GSM, cell reselection to 3G is possible if CPICH Ec/Io of the candidate is above
FDD_Qmin.
Therefore, to avoid ping pongs between 3G and GSM the following condition should be met:
CPICH Ec/Io
QqualMin +Ssearch_RAT
Ssearch_RAT=4 dB
QqualMin=-18 dB
Camping on 3G Measure GSM Camping on 3G
t
How to avoid ping pong ?
Qqualmin = -18dB Ssearch_RAT =2dB -> the 3G->2G cell reselection starts when Ec/No hits -16dB
FDDQmin(GPRSFDDQmin) = -14dB (6) and QsearchP/QsearchI = always
The cell reselection paramters 3G -> 2G and 2G -> 3G provide only 2dB hysteresis which is not enough and should be
noticed from the RNC statistics as high amount of INTR_RAT_CELL_RE_SEL_ATTS from all the RRC Connection
Setup Attempts
Recommendation is to adjust the FDDQmin from -14dB to -10dB (or even up to -8dB) to provide 6 to 8 dB hysteresis
between 3G to 2G cell reselection and 2G to 3G cell reselection
Another parameter to tune is Qrxlevmin
On top of Treselection the above parameters will slow down further the 2G to 3G and 3G to 2G cell reselections
Treselection
How long the reselection conditions must be fulfilled before reselection is triggered?
Treselection
Impacts all cell reselections : Inter RAT, intra frequency and inter frequency
The UE reselects the new cell, if the cell reselection criteria (R-criteria, see next slide) are fulfilled during a time interval
Treselection
As this parameter impacts on all the cell reselections too long Treselection timer might cause problems in high mobility
areas but too short timer causes too fast cell reselections and eventually causes also cell reselection ping pong
Recommended value 1s should work in every conditions i.e. enough averaging to make sure that correct cell is
selected
However careful testing is needed to check the performance of different areas
(Dense) Urban area, slow moving UEs with occasional need for fast and accurate (to correct cell) reselections e.g.
outdoor to indoor scenarios or city highways in some cases cell by cell parameter tuning is performed to find most
optimal value between 0s and 2s but typically 1s is optimal value when workload is considered as well
Highways, fast moving UEs must reselect correct cell typically 1s works the best (however occasionally also 0s
might be needed in fast speed outdoor to indoor cell reselections e.g. tunnels)
Rural areas, slow or fast moving UEs need very often reselect between different RATs and make proper cell
reselections even when the coverage is poor typically 1s works the best
Location Area Borders, usually the coverage is fairly poor typically 1s works the best but sometimes to reduce
location area reselection ping pong 1s is used when going from LA1 to LA2 and 2s from LA2 to LA1
IRATHO
IRATHO
As M1013 described in PartI, M1015 return statistic for intesystem HO. The filtering criteria
can be replicated with the exception of ping-pong
Filtering criteria:
Major
- High number of failures for a defined out-going adjg (failure ADJG)
- high number of fail for a defined source (failure WCEL)
Minor
- very low number of attempt with failure (low used adjg)
- zero number of attempt for declared adjs stabilized value (no adjg)
- high number of attempts for an out-going adjs (unbalanced ADJG)
out-going condition is sufficient
- high number of attempts for a defined source (unbalanced WCEL)
Same procedures can be applied to the case considering that the event related are 1E and 1F
1E/1F Events for CPICH Ec/No and RSCP
HHoEcNo(RSCP)Thres
HHoEcNo(RSCP)Cancel hold
determines the absolute CPICH
e.g. P-CPICH Ec/No
Defines the threshold of Ec/No(RSCP)
that must be exceeded by a measurement Ec/No threshold which is used by the
of an active set cell to be canceled the UE to trigger the reporting event 1F.
Cell 1 event 1F related When the measured CPICH Ec/No of
all active set cells has become worse
Cell 2 than or equal to the threshold in
question, the RNC starts inter-
frequency or inter-RAT (GSM)
measurements in compressed mode
for the purpose of hard handover.
Cell 3
1F
1E
time
HHoEcNo(RSCP)CancelTime
determines the time period during which the CPICH HHoEcNo(RSCP)TimeHysteresis
RSCP of the active set cell must stay better than the determines the time period during which the CPICH Ec/No of the active
threshold HHoRscpCancel before the UE can trigger the set cell must stay worse than the threshold HHoEcNoThreshold before
reporting event 1E. the UE can trigger the reporting event 1F.
IRATHO Triggering reason
6 . Others
5. Quality deterioration report - Load and Service based HO
from UL outer loop PC - IMSI based HO
- Emergency ISHO
FMCG: GSMcauseUplinkQuality
GSMcauseX
These parameters indicates whether a handover to GSM caused by low measured absolute CPICH Ec/No of the serving cell is
enabled (1)
IRATHO Triggering reason
1. CPICH coverage
2. Pilot pollution
3. UL/DL Service coverage
In actual case is possible to dsciminate between low CPICH coverage triggered by high# RSCP
attempts or probable pilot pollution triggered by high # Ec/No attempts
Start
Yes
High # Ec/No? DL Qual limiting DL interference/ Pollution
should be evaluated
DL
Yes
High # RSCP? DL level limiting CPICH power analisys/ new
site required
This condition
should be the
dominannt one
Yes without
High # UE New site required or new
UL level limiting associated
Tx pwr? Parametrization for IRATHO
failure
UL
Yes
Load analisys and UL
High # UL Qual? UL qual limiting interference evaluation
End
Yes
High # DL Service limiting New planning for service is
DPCH? required
IRATHO - Failure
CN
UE Node B RNC
Not enough resources AC reject CM. NBAP: Radio Link Reconfiguration Prepare
IS_COM_MOD_STA_NOT_P OS IS_HHO_W_CMOD j
j
Considering that M1010C2 (INTER SYST COM MOD STA NOT POS FOR RT) is updated if it is
not possible to start inter-system compressed mode measurement due to radio resource
congestion, BTS- or UE-related reasons to have a better insight on radio congestion it could be
better to use, e.g. for UL the M1002C361 REQ FOR COM MODE UL REJECT TO INT SYST HHO
IN SRNC and the M1002C357 REQ FOR COM MODE UL TO INT SYST HHO IN SRNC and use the
following :
M1002C361/M1002C357
NO Cell Found measurement
fail
No Cell Found
Counters
NO Cell Found means:
there is no suitable gsm target cell in terms of RX Level
Compressed
OR Mode start
the target gsm is suitable but its BSIC verification fails
AND HHO Attempt
Counters
the maximum number of measurement reported are received
AND measurement not
maximum measurement interval is not expired fail
The following KPI gives an indication of the number of GSM cell not found
Missing ADJG could be the reason or a dedicated parameter tuning for the 1F event.
The KPI can be madified taling care of the WO_CMOD events
NO Cell Found
Start
High #
NO Cell? End
Yes
Yes
New site
GSMCause=Ec/ Pollution evaluation required
Nol?
Reduce Cancel
Verify Good GSM coverage
in the far field? Increase Time hysteresis
ADJG
Yes Yes
Reduce
End
thershold
DROP & UNSUCCESS IRATHO
Optimization for unsuccess is not possible
because the reason are:
UTRAN Failure
- physical channel failure (the UE is not able to
Counter
establish the phy.
- Protocol error
- Inter-Rat protocol error
UE Failure
Counter - Unspecified
Drop are related to drop call occurred
during the procedure
ISHO Success
Counters In this case the optimization is required and
pass through the evaluate of GSM and 3G plot
coverage. Optimize If necessary number of
ADJG or NWP parameters otherwise tune
RRC Drop RNW parameters.
Counters Thresholds can be relaxed to favourite an
early exit from 3G layer
3G > 2G Unbalancing
This topic present the inherent problem due to the fact that the 2G layer is not involved in
the analisys.
Few consideration can be performed under some assumption:
The following KPIs used over a cluster for CS voice service gives the percentage of the CM
started over all the RAB, giving an idea of the attempted mobility procedure requested for a
cluster where the 3G coverage should be assured
Better to use completes: failures, normal & SRNC reloc on denominator and use the KPI inside the
3G cluster or difining a polygon where 3G service is required
Once Correlated with voice drop due to radio link failure and rrc drop during ISHO, the KPI can
help operator in understand the ISHO strategy. Similar KPI is possible for PS