Professional Documents
Culture Documents
Wcdma: Kpi Analysis & Optimization
Wcdma: Kpi Analysis & Optimization
SRNC
Accessibility: RNC
RRC Setup &
Access Rate Usage:
RAB Setup & Cell Availability
Access Rate Ave. Uplink
Call Setup Success Load
Rate Ave. Downlink
PS setup success Load
Pre-
rate (NRT,HSDPA, HSDPA X emption
HSUPA) Throughput BTS2
UE BTS1 Cell Throughput
X
Retainability:
RRC Drop Rate Mobility:
RAB Drop Rate SHO/ISHO Success
PS success rate Rate
(NRT, HSDPA, SHO Overhead
HSUPA) HDSPA/HSUPA SCC
success
Presentation / Author rate
/ Date
Genuine Call Setup Failure
Scenarios
– RF issue
• Interference / Dominance / Coverage
• Missing neighbour
– System Issue - BTS
• No response to “RRC Connection Request”
• “RRC Connection Reject” to “RRC Connection
Request”
– System issue - RNC
• “CC Disconnect” after “Call Proceeding” due to “DL
RRC Connection Release”
– Core NW
• “CM Service Abort” after “CM Service Request”
– System issue (test number)
• “CC Disconnect” after “CC Progress”
Genuine Drop Call scenarios
RF issue
– Interference / Dominance / Coverage
– Missing Neighbours
System issue BTS
– Sudden “CC Disconnect” due to “DL RRC Connection
Release”
– Sudden drop to idle, no disconnect messaging
4. RAB set-up
6. Service Established
8. Service Released
Call Setup Failure Start
Yes
B
UL coverage & RACH
No
parameter. Optimization AICH(ACK) received? Report & Finish
(changing serving cell) (Check failure cause)
Yes No
“RRC Connection
Setup” received?
No “RRC Setup
Reject” received?
C
Yes Yes
AC optimization (check PrxNoise
Ye
s
E
Report & Finish
Check failure cause
(Not radio problem/cell update)
Call setup failures – MissingA
Neighbour
Missing neighbour analysis over the
whole route (3G-3G, 3G-2G)
Search for failures due to missing 3G-
3G neighbours
Search for failures due to missing 3G –
2G neighbours
– It is suggested to place 2G scanner to the test vehicle
Call Setup Failure Analysis-B
Block B -
The purpose of this activity is to check
the Random Access Process is
working adequately by investigating
whether AI (Acquisition Indicator) has
been received through DL AICH
If AICH was not received by UE, the
cause of the problem can be
classified into:
– Inadequate RAN parameter related to
Random Access: RAN parameter
Call Setup Failure Analysis-B
UE Block
WBTSB - RNC
Preamble/RACH
Acquisition Indicator/AICH
L1 Synchronisation
UE in CELL_DCH state
RACH Process B
L1 ACK / AICH
Downlink Not detected
BS
UEtxPowerMaxPRACH
PowerRampStepPRACHpreamble
…… ……
Uplink
MS Preamble Preamble Message part
1 2
PowerOffsetLastPreamblePRACHmessage
PRACH_preamble_retrans
# PRACH preambles transmitted during one PRACH cycle without receiving AICH response
RACH_tx_Max
# preamble power ramping cycles that can be done before RACH transmission failure is reported
Yes
Yes
Is UL Interference Report
Reportthere
theremight
mightbebean
aninterfering
interfering
abnormally HIGH? source
source Nearby the servingcell
Nearby the serving cell
No
Change
Changethe
theServing
Servingcell
cellto
tocover
coverthe
theproblem
problemArea
Area
=> UE is too far to reach the serving cell
=> UE is too far to reach the serving cell
Call Setup Failure Analysis-B
Block B
– Overload Area:
• If measured UL (PrxTotal) or DL (PtxTotal) load exceeds
Call Setup Failure AnalysisC
• During the pre-optimization phase it is unlikely that AC will stop an RRC
connection setup during the drive testing because there are normally very few UEs
in the network. (Traffic loading is trivial)
• However, it should be checked that measured PtxTotal and PrxTotal are less than
PtxTarget (e.g. 40dBm) and PrxTarget (e.g. 4dB, 60% loading) respectively.
• If DL AC does not allow RRC setup check the Tx power of WBTS, # of
channels transmitted, Signaling messages.
• If UL AC does not allow RRC setup: Check out if there is an interfering source
nearby the serving cell.
Call Setup Failure AnalysisD
To check if Layer 1 Synchronization
(slot/frame sync) has failed
If “RRC Connection Setup” was received by UE but UE does not send
“RRC Connection Setup Completed”, we will report “L1
synchronization failure” and have to check L1 system messages.
Call setup failures – SystemE
• “CC Disconnect” after
issue RNC
“Call Proceeding”
• Good RF conditions
• Failures in RAB setup
occur between the “RAB
Assignment Request”
being received from Core
Network and the RAN
sending out Radio
Bearer Setup. Therefore
the failure is between
BTS and Core Network.
Call setup failures – SystemE
• “CC Disconnect” issue RNC
after “Call
Proceeding” (cont.)
• An example (site
shows high values
on counter
“RAB_STP_FAIL_CS
_VOICE_BTS”
during the drive test
• In the recent check
the counter showed
no failures.
Call setup failures – Core E
“CM Service Abort” after
“CM Service Request”
NW
Good RF conditions
“Security Mode
Command”-message
not received by UE,
thus the failure is
believed to be at Core UE Node B RNC MGW
Network.
RR C Connection E stablishment
• The NAS message is not read by the RNC but is forwarded to ultimedia
the m gateway. The NAS
message includes the IMSI as a UE identity
• The SCCP : Connection R equest
message establishes the connection orientated signallingnlink i
the same way as it was for the R RC connection phase.This does
t reserve
no any resources for the
AMR call itself.
• The Connection Confirmmessage identifies the RNC with a destination local reference
hichwis the
same as the source reference within the
Connection Requestmessage
• The Connection Confirmmessage identifies the CS core with a source local reference
• The CS core sends aRANAP: Location Reporting Control
message to the RNC requesting
information regarding the location of a particular UE
• The RANAP: Common IDmessage specifies the IMSI belonging to the UE
• The Security Mode Command
message triggers the start or stop of ciphering and integrity
protection.
Call setup failures – SystemE
Issue
“CC Disconnect”
Progress”
after “CC (test number)
Cause: recovery
on timer expiry
State Transition triggers
Phys. Reconfiguration
After RT call with inactive
Frequent cell updates PS RABs
Phys. Reconfiguration Fast call setup from
URA Update, UL data, Paging UTRA RRC Connected Mode CELL_PCH
URA_PCH CELL_PCH
RB. Reconfiguration
Traffic Volume, RACH load
RRC Setup / Release
RB. Reconfiguration
Inactivity Timer, Overload
IDLE Mode
State Transition triggers
IDLE
DCH
IDLE
CELL_DCH State
• DCCH and – if configured –
DTCH
• Dedicate physical channel in
use
• UE location known on active
set cell level
• UE responsible for
measurement reporting
• Cell system information on
BCCH
• RRC messages on DCCH active set
cell
active set
cell
RNC
supply
area
URA 2
URA 3
27 © 2006 Nokia Layer 3 (RRC) /
Kittipong Thamapa
RU20 New Counters &
Measurements
/
Cell Availability
RNC_183c Cell Availability KPI counts Cell availability from
user point of view:
100 * sum( AVAIL _ WCELL _ IN _ WO _ STATE )
Cell _ Availability =
sum( AVAIL _ WCELL _ EXIST _ IN _ RNW _ DB )
Setup Failure
Cell and Neighbour Cause? setup
Cells availability Sites OK ? Setup
Alarms/Tickets /Access
RNC Troubleshooting
Yes
BTS/TRANS/FROZBS
setup AC UL/DL
Setup Interference Access
/Access (DL codes)
Capacity Optimisation
Access
Yes
3G cell at
SRNS Relocation
inter-RNC
troubleshooting
border ?
NO
Interference
Coverage/Interf
RF Optimisation
erence
Coverage
RRC: Initial Direct Transfer RRC ACTIVE fails when an interface related (Iu, Iur , Iub, or
Radio) or RNC internal failure occurs, and the failure causes
RANAP: Initial UE Message the release of the RRC Connection. When an RRC active failure
occurs, the RRC send a RANAP: IU RELEASE REQUEST to all
UE-CN Signalling
involved CNs and waits for RANAP: IU RELEASE COMMAND
(E.g. RAB Establishment and Release)
message (s)
RRC: RRC connection Release RRC ACTIVE release cause can be either
RRC: RRC connection Release Complete ISHO, IFHO, SRSN relocation or pre-
Release RRC resources in RNC, BTS,
emption
Transport
UE
Active
BTS RNC CN
RANAP: RAB Assignment Request with IE: RAB reconfiguration RAB ACTIVE fails when an interface related (Iu, Iur, Iub, or
Radio) or RNC internal failure occurs, and the failure causes
RAB Holding Time
coming call request can not be handled due to lack of ICSU processing
No hand free” is RNC internal clear code.
UE BS RNC
Success
dropped, also active RAB is
Setup Access Complete dropped.
Complete Complete
Access
RAB setup
Active Attempts to start the call
Release RAB setup access
Attempts
/
Call Setup Success Rate
(CSSR)
CSSR KPI for CS voice from end user perspective (RNC 565f)
100 * ( sum( MOC _ CONV _ CALL _ ATTS − MOC _ CONV _ CALL _ FAILS
+ MTC _ CONV _ CALL _ ATTS − MTC _ CONV _ CALL _ FAILS
+ EMERGENCY _ CALL _ ATTS − EMERGENCY _ CALL _ FAILS
− RRC _ ACC _ REL _ EMERGENCY − RRC _ ACC _ REL _ MO _ CONV
− RRC _ ACC _ REL _ MT _ CONV ) ( sum( RAB _ ACC _ COMP _ CS _ VOICE )
AMR _ CSSR = *
sum( MOC _ CONV _ CALL _ ATTS + MTC _ CONV _ CALL _ ATTS sum( RAB _ STP _ ATT _ CS _ VOICE ))
+ EMERGENCY _ CALL _ ATTS − RRC _ ATT _ REP _ MO _ CONV
− RRC _ ATT _ REP _ MT _ CONV − RRC _ ATT _ REP _ EMERGENCY
− RRC _ ACC _ REL _ EMERGENCY − RRC _ ACC _ REL _ MO _ CONV
RRC − RRC _ ACC _ REL _ MT _ CONV − RRC _ CONN _ STP _ REJ _ EMERG _ CALL ) RAB
part part
RRC request repetitions done by UE after RRC reject are excluded from
denominator (not necessarily seen as failures from the user's
perspective)
– Emergency calls re-directed to GSM layer are excluded from
denominator
The occurred cell re-selectionsPresentation
are subtracted
/ Author / Date both from the numerator
and denominator because they are not considered as call attempts
_PACKET CALL SETUP
SUCCESS RATE
RRC request repetitions done by UE after RRC reject are included in the formula
* The occurred cell re-selections are subtracted both from the numerator and
denominator because they are not considered as call attempts from mobile end-
user point of view. The UE has made/ Author
Presentation a new RRC connection via another cell and
/ Date
Attempts-counter is updated in the new cell for the new attempt.
Low in CSSR:
RRC Conn Setup & Access
Failure Counters
Analysis
RRC_CONN_STP_FAIL_AC
Check UL Interference, DL Power & Code occupancy if there is need to upgrade radio capacity
RRC_CONN_STP_FAIL_BTS
Evaluate NBAP counters (radio link reconf. Failures) and KPIs for troubleshooting BTS resources
Check BTS configuration in terms of CE allocation – Use Channel Element (5001) Counters in order to
evaluate lack of Channel Elements
Expand the Capacity or decrease the traffic offered to the site until the problem is solved
In case BTS is not responding delete and re-create COCO
RRC_CONN_STP_FAIL_TRANS
Evaluate Number of reconfiguration failure due the transmission
Check COCO Configuration
Expand the capacity or decrease the traffic offered to the site until the problem is solved
RRC_CONN_STP_FAIL_RNC
Typically RNC fault or Incoming SRNC Relocation Failure (inter-RNC border)
Required ICSU log tracing if no RNC fault or SRNC relocation problem
Communicate the problem to Care department
RRC_CONN_ACC_FAIL_RADIO
Dominant failure causes due to wrong UL or DL coverage
UL Coverage -> Check if cell is affected by an external interference (Thermal Noise measurements).
DL Coverage -> Tune SCCPCH Power if UE does not receive the RRC Setup Message
-> If UE does not synchronize, reduce N312 from 2 to 1 (depends on UE model) or tune CPICHToRefRABOffset
vs.
Qqualmin (or Qrxlevmin)
RRC_CONN_ACC_FAIL_MS
UL Coverage -> Tune Cell Dominance (or CPICH) in order to balance UL and DL (if UL interference if not the cause).
Check if cell is affected by an external interference (Thermal Noise measurements).
RAB_STP_FAIL_XXX_BTS
Evaluate NBAP counters (radio link reconf. Add failures) and KPIs for troubleshooting BTS resources
Check BTS configuration in terms of CE allocation – Use Channel Element (5001) Counters in order to evaluate lack
of Channel Elements
Expand the Capacity or decrease the traffic offered to the site until the problem is solved.
In case BTS is not responding delete and re-create COCO
RAB_STP_FAIL_XXX_TRANS
Evaluate Number of reconfiguration failure due the transmission
Check M1005C128 CANC_ADD_SRNC_TRAN_STP_FAIL
Check RAB_STP_FAIL_XXX_IUB_AAL2, M1001C531-C533
Check COCO Configuration
RAB_STP_FAIL_XXX_RNC
Typically RNC fault or Incoming SRNC Relocation Failure (inter-RNC border)
Required ICSU log tracing if no RNC fault or SRNC relocation problem
Communicate the problem to Care department
Evaluate Cell resource Prx and Ptx parameters (same as RAB_STP_FAIL_XXX_AC Case)
RAB_ACC_FAIL_XXX_RNC
YES 3G cell
To 3G cell at
covers over
p inter-RNC
a coverage
iss border ?
No cell hole ?
ue
s found YES RF and ISHO neighbour
ratio >40 optimisation
Core: Inners / Outers %
audit
NO
2G : TCH blocking No cell found
ISHO ratio > 90 % Coverage issue (new site
3G : Wrong N’ YES Success and enough needed)
borgs definition Rate < ADJG
95%
No
ISHO Yes
Failure ISHO Failed
Analysis No
No
Best server’s No
Coverage Optimization
RSCP> -102dBm
Missing No
Dominance Optimization
Neighbour
Best server’s
A
Ec/No> -12dB Yes Neighbour list
Optimization
B Investigate possible
BTS or RNC problem
Check Iur
SHO Analysis Yes
Inter RNC HO
Check neighbor definition parameters
No
Yes No DL ASU
Fix SC Clash SC Clash
C No
received
Yes
No Yes
DL Tx No Load Optimisation/
Uplink Yes
Power Max Interference External Interferer
Yes No
D
CPICH Optimisation
Link Yes
Unbalanced
No
Presentation / Author / Date
A
Drop call failures – RF issue
RF drops mostly due to poor
dominance or interference
Poor coverage could lead to ISHO,
although poor dominance or
interference can cause ISHO to fail.
Rapid field drop can cause drop due
to coverage
Poor dominance or interference can
cause Compressed Mode (CM) to
start even if RSCP is still good.
In CM UE transmits with higher
power (more interference) and
spends less time on 3G (less
accurate measurement reporting)
Poor dominance or interference can
lead to Active Set update failures Poor dominance
and eventually to drop call. causes Active Set
update failures
TrChAgg and DL
DPCCH BER high
Transport
Channel BER. Btw
UE<->RNC (MAC
layer)
Drop to
IDLE
Sum of UL PC
commands < 1500,
UE not receiving all
the PC commands.