WCDMA : KPI ANALYSIS & OPTIMIZATION

Network planning& Optimization

 Illustration on RAN KPI-RU20
SRNC
Relocation
RNC

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

System issue RNC

– Sudden “CC Disconnect” due to “DL RRC Connection
Release”
 KPI Definitions
The KPIs to be monitored from the RAN could be:
– Cell availability
– Call Setup Success Rate (CSSR)
– Call Drop rate
– SHO/ISHO/HSPA SCC success rate
– Packet Session setup/success rate (NRT, HSDPA, HSUPA)
In NOLS:
– RNC counter description
– NetAct DB description for RNC measurements
– WCDMA RAN Key Performance Indicators
– Key Indicator Changes
– Measurement Changes

Presentation / Author / Date

 AMR CS Call Phases
UE WBTS DRNC SRNC CN

1. Cell search, BCCH

decoding & RACH access

2. RRC connection set-up

3. UE <--> CS-CN signalling

4. RAB set-up

5. UE <--> CS-CN Signalling

6. Service Established

7. Branch addition/deletion & Active set update

8. Service Released
Call Setup Failure Start

Analysis A Coverage Optimization

Process__DT
Best server’s No
RSCP > -102dBm
Missing No
Dominance Optimization
Yes Neighbour ?
Best server’s No
Yes Neighbour list Optimization
Ec/No > -12dB

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

D Report & Finish

(Reason of problem: L1 sync fail)
No (DCH) “RRC Connection setup
Completed” sent from UE?
& interferer around BTS)

Report & Finish

Yes

Report & Finish No “Radio Bearer setup

(Check failure cause) failure”Received?

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

RRC: RRC Connection Request/PRACH

NBAP: RADIO LINK SETUP REQUEST
NBAP: RADIO LINK SETUP RESPONSE

RRC: RRC CONNECTION SETUP/FACH

L1 Synchronisation

NBAP: SYNCHRONISATION INDICATOR

RRC: RRC CONNECTION SETUP COMPLETE/DCH

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

Initial preample power:

•Ptx = CPICHtransmissionPower-RSCP(CPICH) +RSSI(BS) +
PRACHRequiredReceivedCI
 Call Setup Failure Analysis-B
Block B-
Solutions for RACH
Max UE Tx power hit
optimisation
No
To
Toincrease
increasePRACH_Preamble_retrans
PRACH_Preamble_retrans
the UE_P_MAX(24dBm)? Or
OrPowerRampStepPRACHPreamble
PowerRampStepPRACHPreamble

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

Open loop Power

Control parameters from
RACH Info message
 Call setup failures – SystemC
issue
No response to “RRC Connection
–
BTS
Request”
Good RF conditions
– Wrong MHA settings or cable loss settings can cause the site not to
“hear” the UE
– PrxNoise statistics, receive link parameters and HW units to be
checked (faulty MHA, wrong MHA parameters, wrong cable / feeder
loss parameters, faulty units)
 Call setup failures – SystemC
issue BTS
“RRC Connection Reject” after “RRC
Connection Request”
– Good RF conditions
– Admission Control can reject too many (or
admit too many) connection requests due
to wrong PrxNoise measurements.
– PrxNoise statistics, receive link parameters
and HW units to be checked
 Call Setup Failure Analysis C
UE has the appropriate DL/UL coverage but if RNC does not allow to set
up the RRC connection of the requested RAB (Radio Access Bearer),
Call setup will fail.
Admission Control (AC) is involved in RRC connection setup. AC can
reject RRC reject RRC connection Setup due the DL Load, UL load or
DL Spreading codes

– Marginal Load Area:

• If measured UL (PrxTotal) or DL (PtxTotal) load exceeds
target thresholds (PrxTarget and PtxTarget) AC can still
admit new RAB to the cell if a new non-controllable load
keeps below target thresholds (in practice this means that
AC can admit only new controllable load RABs i.e. NRT RABs)

– 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

Initial Direct Transfer (CM Service Request) SC CP : Connection R equest

S CCP : Connection Confirm

Location Reporting Control
Common ID
S ecurity Mode Command

• R R C: Initial Direct Transfer

message is sent using acknowledged mode R LC to the CS core
domain. Routing is to be based upon the local
-TMSI
P

• 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

The call goes via IN SCP to a
recording.
A static test was done by Nokia
Customer Care and in few
instances the call dropped after
30 seconds of recording passed.
Hence the problem is associated 30
with the test number not the sec
RAN

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

Fast call setup from

URA_PCH
Phys. Reconfiguration UL/DL
After RT call with inactive PS RABs activation timer
& high mobility in CELL_DCH
CELL_FACH Phys. Reconfiguration
CELL_DCH
Cell Update, UL data, paging

RB. Reconfiguration
Traffic Volume, RACH load
RRC Setup / Release
RB. Reconfiguration
Inactivity Timer, Overload
IDLE Mode
State Transition triggers
IDLE

Call Setup 1.2 sec

DCH

Transition DCH-FACH due

to inactivity  10 sec
)Parameter)

FACH Transition FACH-PCH du

to inactivity  2 sec
PCH )Parameter)
FACH

DCH Wake up time PCH – DC

due to activity  3 sec

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

25 © 2006 Nokia Layer 3 (RRC) /

Kittipong Thamapa
 CELL_FACH
• DCCH State
and – if configured –
DTCH
• FACH used for higher layer
data transfer,
• UE monitors FACH
permanently
• Uplink transmission on
RACH
• UE location known on
serving cell level
• UE performs cell re-selection
• UE responsible for serving
measurement reporting cell
• Cell system information on
BCCH
• RRC messages on BCCH,
CCCH and DCCH

26 © 2006 Nokia Layer 3 (RRC) /

Kittipong Thamapa
 CELL_PCH• no
and URA_PCH State
DCCH and DTCH
• Before uplink transmission ⇒ UE moves to
CELL_FACH
• UE must be paged
• RRC messages on BCCH and PCCH
• In CELL_PCH
- UE location known on cell level
- UE performs cell re-selection and cell
updates
• In URA_PCH
- UE location known on URA level
- UE performs cell re-selection and URA
updates
•one or several cells
URA – UTRAN Registration Area
•independent from LA
URA 1

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 )

M1000C178 AVAILABILITY WCELL IN WORKING STATE

• # of samples when WCELL is in WO State. Counter M1000C180 is always updated along with this counter
• Counter is updated with the value 1 once in approx. 5 seconds when the WCELL is in WO State
M1000C180 AVAILABILITY WCELL EXIST IN RNW DATABASE
• # of samples when WCELL is configured in the database. This counter is used as a denominator for cell
availability calculation
• Counter is updated with the value 1 one in approx. 5 seconds when the WCELL is configured in the radio
network database

Presentation / Author / Date

 Cell Availability
– There is also Optional Cell availability KPI, which counts
Cell Availability from network point of view. Situation
where WCELL is blocked by User are excluded from the
formula.
– RNC_727a Cell Availability 100KPI,
* sum(excluding
AVAIL _ WCELL blocked
_ IN _ WO _by
STATE )
Cell _ Availabili ty _ excluding _ BLU
user state (BLU), Counts Cell_ state = availability from network
 AVAIL _ WCELL _ EXIST _ IN _ RNW _ DB 
sum  
point of view:  − AVAIL _ WCELL _ BLOCKED _ BY _ USER 

M1000C179 AVAILABILITY WCELL BLOCKED BY USER

• # of samples when WCELL is BLU State. Counter M1000C180 is always updated along with
this counter
• Counter is updated with the value 1 once in approx. 5 seconds when the WCELL is in BLU
state

Presentation / Author / Date

CSSR definition

DNO Optimization Processes / JC

Ejarque
 Low in CSSR?
Identify call setup failure
Call phases
Setup Phases
CSSR affected if any of the
followings take
place.
1. RRC Conn. Setup Fail
2. RRC Conn. Access Fail
3. RAB Setup Fail
4. RAB Setup Access Fail

Call Setup Success Call Drop

Call Setup Phase Connected

RRC RRC RRC RRC RAB Setup RAB Drop

Conn. Req Conn. Setup Conn. Acc Conn. Act

DNO Optimization Processes / JC

Ejarque
 Low in CSSR?
RRC/RAB Setup & Access Analysis
Process Flow Chart
Top (N) RRC Setup
and Access failures
Top (N) RAB Setup
and Access failures

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

DNO Optimization Processes / JC

Ejarque
 Call Setup Success Rate
(CSSR)
Poor CSSR could be a result of
– Poor coverage or dominance or interference issues in Radio
interface
– Capacity issues in Radio or Iub interface
– Configuration issues in WBTS (parameters or HW)
CSSR is essentially RRC Setup Success * RAB Setup Success
(or successful PS session setups in case of PS call)
CSSR covers all the steps from the initial RRC connection request
from the UE to the network, through the RRC setup phase and
the RAB setup phase, and until user data is starting to get
transferred.

The CSSR formulas are for different traffic classes like:

– CS voice calls (RNC 565 f)
– CS video calls (RNC 566e)
– PS RT Streaming Calls (RNC 575 d)
– PS NRT Calls (Interactive & Background) (RNC 576d)

Presentation / Author / Date

 Definition of Call Set-Up
UE Success Rate (CSSR)
RRC: Connection Request
BTS RNC CN

RRC Connection Setup phase

Resource Reservation in RNC, BTS, Transmission
RRC: RRC Connection Request Setup
RRC Connection Access phase
RNC waits reply from UE

RRC: RRC Connection Completed

RRC: Initial Direct Transfer cm service request
RANAP: Initial UE Message
DIRECT TRANSFER (Call Call Set-
Proceeding) up
RANAP: RAB Assignment Success
Request
RAB Connection Setup phase Rate
Resource Reservation in RNC, BTS, Transmission
RRC: Radio Bearer Set- Call Set-
up up Time

RAB Connection Access phase

RNC waits reply from UE
RRC: Radio Bearer
Setup Complete
RANAP: RAB Assignment
DIRECT TRANSFER (Alerting) Response
DIRECT TRANSFER (Connect)
DIRECT TRANSFER (Connect
Acknowledge)

Presentation / Author / Date

 RRC Connection Setup &
UE
Access and Active
BTS RNC CN

RRC: RRC connection Request

RRC SETUP fails if some of the needed resources (RNC, BTS,
RRC SETUP phase AIR, Transport) are not available. When an RRC setup failure
occurs the RNC sends an RRC: RRC CONNECTION REJECT
RRC Setup time

(Resource Reservation in RNC, BTS,

Transport) message to UE
RRC: RRC connection Setup
RRC ACCESS fails if the UE does not reply to RRC: RRC
RRC ACCESS phase
CONNECTION SETUP message with the RRC: RRC CONNECTION
(RNC waits for Reply from UE) SETUP COMPLETE message in given time, if the BTS reports a
RRC: RRC connection Setup Complete radio link synchronisation failure or in an RNC internal failure
occurs
RRC ACTIVE phase

RRC: Initial Direct Transfer
RANAP: Initial UE Message
UE-CN Signalling
(E.g. RAB Establishment and Release)
RRC ACTIVE fails when an interface related (Iu, Iur , Iub, or
Radio) or RNC internal failure occurs, and the failure causes
the release of the RRC Connection. When an RRC active failure
occurs, the RRC send a RANAP: IU RELEASE REQUEST to all
involved CNs and waits for RANAP: IU RELEASE COMMAND
message (s)

RANAP: Iu Release Command

RRC: RRC connection Release
RRC: RRC connection Release Complete
Release RRC resources in RNC, BTS,
Transport
RRC ACTIVE release cause can be either
ISHO, IFHO, SRSN relocation or pre-
emption

Presentation / Author / Date

 RAB Setup & Access and
RAB Access failures are
not so Common

UE
Active
BTS RNC CN

RRC Connection Active Phase, UE-CN Signalling

RAB SETUP fails if some of the needed resources (RNC, BTS,
AIR, Transport) are not available. When an RAB setup failure
occurs the RNC sends a RANAP: RAB ASSINGMENT RESPONSE
RANAP: RAB Assignment Request message to the CN with an appropriate failure cause
RAB SETUP phase
RAB Setup time

(Resource Reservation in RNC, BTS, Transport)

RAB ACCESS fails if the UE replies with an RRC: RADIO BEARER
RRC: Radio Bearer Setup SETUP FAILURE message or the connection cannot be
RAB ACCESS phase established in a give time. When a RAB access failure occurs,
(RNC waits for Reply from UE) the RNC sends a RANAP: RAB ASSINGMENT RESPONSE
message to the CN with an appropriate failure cause.
RRC: RB Setup Complete
Immediately after this, the RNC sends also a RANAP: IU
RANAP: RAB Assignment Response
RELEASE REQUEST to the CN and waits for RANAP: IU RELEASE
RAB ACTIVE phase COMMAND message
(User Plane Data Transfer)

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

RAB Reconfiguration Actions

(Reconfigure RAB resources in RNC, BTS,
Transport)
RRC: RB Reconfiguration
RRC: RB Reconfiguration Complete
RANAP: RAB Assignment Response
RANAP: RAB Assignment Request with IE: RAB Release
RRC: Radio Bearer Release
RRC: Radio Bearer Release Complete
RANAP: RAB Assignment Response
Release RAB resources in RNC, BTS,
Transmission
Presentation / Author / Date
the release of the RAB connection.
• If the UE has more than one RAB connection and the failure
is not so critical that it would lease to an RRC Connection drop,
only the failed RAB connection is released. The RNC sends a
RANAP: RAB RELEASE REQUEST message to the CN and waits
for a RANAP: RAB RELEASE COMMAND or RANAP: IU RELASE
COMMAND from CN
• Otherwise, both the RRC connection and RAB connection (s)
are released. The RNC send a RANAP: IU RELASE REQUEST
message to the CN and waits for a RANAP: IU RELEASE
COMMAND MESSAGE from the CN
 RRC connection set up
failure
RRC Connection
o processing is rejected ICSU can not process the call
power on ICSU unit

coming call request can not be handled due to lack of ICSU processing
No hand free” is RNC internal clear code.

UE BS RNC

RRC Connection Request ICSU overload

RRC Connection Reject

Cause: congestion

Failure Counter M1001C618

 Call Setup Failures
RRC and RAB phases
RRC connection setup
RAN resources are reserved for
signaling connection between UE
and RNC
Phase: Setup Access Active RRC access
Connection between UE and
RRC
RRC active
Active UE has RRC connection. If

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

RRC RAB active phase

Active UE has RAB connection
Drop
Failures
CSSR affected if any of the followings
take
Access failures place.
• RRC Conn. Setup Fail
• RRC Conn. Access Fail
Setup failures
• RAB Setup Fail
(blocking)
• RAB Setup Access Fail

Presentation / Author / Date

Call setup Success rate
-CSSR

/
 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

Presentation / Author / Date

 PS Call Setup Success Rate
(CSSR)
RNC_576d- Packet Call Setup Success Ratio [%] over the
reporting period.
Includes both Interactive and Background PS calls
100 * ( sum( MOC _ INTER _ CALL _ ATTS − MOC _ INTER _ CALL _ FAILS
+ MOC _ BACKG _ CALL _ ATTS − MOC _ BACKG _ CALL _ FAILS
+ MTC _ INTER _ CALL _ ATTS − MTC _ INTER _ CALL _ FAILS
+ MTC _ BACKG _ CALL _ ATTS − MTC _ BACKG _ CALL _ FAILS
+ EMERGENCY _ CALL _ ATTS − EMERGENCY _ CALL _ FAILS
− RRC _ ACC _ REL _ INTER − RRC _ ACC _ REL _ MO _ BACKG ( sum( RAB _ ACC _ COMP _ PS _ INTER
− RRC _ ACC _ REL _ MO _ INTER − RRC _ ACC _ REL _ MT _ BACKG ) + RAB _ ACC _ COMP _ PS _ BACKG )
PS _ CSSR = *
sum( MOC _ INTER _ CALL _ ATTS + MOC _ BACKG _ CALL _ ATTS sum( RAB _ STP _ ATT _ PS _ INTER
MTC _ INTER _ CALL _ ATTS + MTC _ BACKG _ CALL _ ATTS + RAB _ STP _ ATT _ PS _ BACKG ))
− RRC _ ATT _ REP _ INTER − RRC _ ATT _ REP _ MO _ INTER
− RRC _ ATT _ REP _ MO _ BACKG − RRC _ ATT _ REP _ MT _ BACKG
− RRC _ ACC _ REL _ INTER − RRC _ ACC _ REL _ MO _ BACKG
RRC − RRC _ ACC _ REL _ MO _ INTER − RRC _ ACC _ REL _ MT _ BACKG )) RAB
part part

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_STP_FAIL_RNTI ALLO FAIL

RNC decides to reject RRC connection request due to RNTI allocation failure caused by RRMU overload

DNO Optimization Processes / JC

Ejarque
Low in CSSR:
RRC Conn Setup & Access
Failure Counters
Analysis
RRC_CONN_STP_FAIL_IUB_AAL2_TRANS
Updated when there is shortage or blocking of AAL2 resource
A subset of RRC_CONN_FAIL_TRANS which include ERQ/ECF fail due to some reason such as DMPG
problem in RNC + ERQ/ECF fail due to transport resource needed in RNC between RNC/MGW

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).

DNO Optimization Processes / JC

Ejarque
Low in CSSR: Failure Counters
RAB setup & Access Fail Root Cause Analysis: RT and NRT
(I/B) domains
RAB_STP_FAIL_XXX_AC
Check UL Interference, DL Power & Code occupancy if there is need to upgrade radio capacity using the already
distributed Nokia Capacity Check BO report.
Check PrxTarget / PrxOffset / of the affected cells

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

DNO Optimization Processes / JC

Ejarque
Low in CSSR: Failure Counters
RAB setup & Access Fail Root Cause Analysis: RT and NRT (I/B)
domains
RAB_ACC_FAIL_XXX_UE

Evaluate Cell resource Prx and Ptx parameters (same as RAB_STP_FAIL_XXX_AC Case)

RAB_ACC_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.

DNO Optimization Processes / JC

Ejarque
 High in DCR?
Top (N) drops
Neighbours’ Performance
Traffic
(use SHO success per adjs
Cell and its Neighbour counters to identify badly
Cells availability performing neighbours) & Map
Site OK ? Audit adjacent sites for
Alarms/Tickets alarms, Availability,
configuration and
YES capacity
Configuration & NO
Parameter audit Conf OK ?
3G Cell at Iur
RNC YES Investigation Iur
performance
YES border?
SHO
SHO Success YES
Rate <
90%?
NO New site ?

ISHO ISHO NO Analyse last detailed RF and IF/IS HO

Failures radio measurements neighbour optimisation

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%

DNO Optimization Processes / JC

Ejarque
 Call drop analysis process Start

SHO Failure Yes SHO Failed

Analysis

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

Presentation / Author / Date

 Call Drop Analysis process –
Start

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

Load Yes Congestion No

UE Tx
Optimisation on target cell Check RF Levels
Power Max

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

Presentation / Author / Date

 A
Drop call failures – RF issue

DL synchronisation is lost ->

UE has stopped transmitting

TrChAgg and DL
DPCCH BER high

Presentation / Author / Date

 A
Drop call failures – RF issue
Fairly good
CPICH Pilot
EcNo

Transport
Channel BER. Btw
UE<->RNC (MAC
layer)

Sometimes DPCCH BER (btw UE<-

>WBTS) can be a better indicator of
what's happening to the dedicated
channel than the CPICH EcNo, in
particular in the case that power control
may not be tracking well

Presentation / Author / Date

 Drop Call Failures – System B
issue BTS
Sudden drop to idle, no disconnect messaging
– Site malfunctions to be checked
– In the example below site had faulty unit (WTR)

Drop to
IDLE

Presentation / Author / Date

 Drop Call Failures – System B
“CC Disconnect” due to Issues RNC DPCCH
BER
“DL RRC Connection
Release”
No response to UL
Measurement Reports
In the example site had no
alarms, good RF & BER
Not able to add SC265 to
Active Set, next call on the
same cell => no failure.
Difficult to troubleshoot if
the failure does not
happen systematically =>
follow up in the next
weeks drive / do a
separate drive test in the Sudden “RRC
area Connection
Release”

Presentation / Author / Date

 Drop call failures (SC C
Sudden drop to idle conflict)
Transport
channel
mode (no disconnect
messaging) BLER 100%
Cause of the failure:
overshooting site and
SC reuse
Short term solution to
add overshooting
neighbour in ADJS
definitions

Cell ABC, SC258

Presentation / Author / Date

Drop call failures – Uplink D
Interference UL interference from the
SIB7 message

Presentation / Author / Date

 Drop call failures – Link D
help indicating problems in link Balance
UL & DL Power Control commands can UE RX power control
balance. message: DL reception
weak -> UE is ordering
PC frequency is 1500 Hz, thus ideally the WBTS to increase power.
sum of PC commands to increase or
decrease power is 1500
E.g. if the sum of UL PC commands is <
1500, this would indicate UE is starting to
loose synchronization
in Compressed Mode there is less PC
commands, UE spends time on 2G

Sum of UL PC
commands < 1500,
UE not receiving all
the PC commands.

Presentation / Author / Date

 Drop call failures – System
issue RNC or BTS ?
“CC Disconnect” due to “DL RRC Connection Release” is just a
consequence of failure which can be due to different reasons
– From UE point of view L3-messaging does not identify
the point of failure distinctly
– BTS or RNC failure? => Suspect BTS first, then RNC
Rule out BTS failures
– Check the site performance from Counters (Iub, Service level,
cell resources SHO, etc) and that site is carrying traffic
– PrxNoise, receive link parameters, alarms
– SC–reuse
– UE performance ?
Identified causes for Active Set Update failure
– “Deaf” sites (PrxNoise)
– Faulty HW
– SC-reuse Presentation / Author / Date
/
 HSDPA low
• Low HSDPA throughput root causes analysis process
throughput? START
OSS counters
measurement data
collection
If throughput is low in
Identify network level, the
Low reason can be also
throughput NO FTP/HTTP server
areas if settings (fire wall),
exist Measurement tools
etc.
No Optimisation
YES Low
Required
through
put due NO
to low
Ec/No
YES or CQI Identify reason for low
If low throughput throughput if not RF
due to low Ec/No or • Mobility (cell change too
Poor CQI, identify frequent)
reason • No HSDPA coverage
• Bad Coverage • Iub / Iu User Plane
Planning Capacity
• Quality issue due • Other HSDPA users in Business Object report
the neighbour same WBTS/Cell already delivered in
planning
• HSDPA Start order to measure all
• DCHParameter
traffic too High (DPA,
Parameters are Optimisation
HSDPA by tuning
Priority) related HSDPA
correctly set up throughput KPIs
• HSPDA Mobility
• Change Antenna parameters (FMCS)
tilt etc.
• PtxMaxHSDPA (WCEL)
• Dynamic Flow Control set
Implement to ON (WBTS)
Changes

DNO Optimization Processes / JC

Ejarque
 RU10 Reporting Suite
Report Topic Name Report Name Report ID
• RNC level 1. System Program System Program RNC Level RSRAN084
1. System Program System Program Cell Level RSRAN000
system program 2. Capacity RNC Capacity RSRAN068
2. Capacity Node B Capacity RSRAN066
added 2. Capacity Cell Capacity RSRAN067
2. Capacity NRT Radio Bearer Statistics RSRAN013
• Corrections to 3. Service Level Service/Session Accessibility Analysis RSRAN073
3. Service Level Service/Session Retainability Analysis RSRAN079
Capacity report 3. Service Level RAB Holding Times RSRAN021
3. Service Level Service Summary RSRAN003
• Modifications to 4. Traffic Allocated Traffic Amounts (R99 + HSPA) RSRAN070
Service level 4. Traffic
4. Traffic
Cell Data Volume and Throughput at RNC
Traffic Summary
RSRAN077
RSRAN026
report 4. Traffic
4. Traffic
Used CE Capacity per RB Type in RNC
Utilization Shares of Total Traffic Allocation Amounts
RSRAN022
RSRAN071
(Streaming class 5. Mobility and Handover Active Set Size for NRT-RT Traffic RSRAN078
5. Mobility and Handover HSPA Serving Cell Change RSRAN033
added+ some 5. Mobility and Handover IFHO Adjacencies RSRAN044
5. Mobility and Handover Inter-System Handover per Cause RSRAN019
other
RNC_169e:DR 5. Mobility and Handover Inter-System Handover Performance RSRAN023
corrections)
+ GAN HO 5. Mobility and Handover
5. Mobility and Handover
Inter-System Handover Reasons
ISHO Adjacencies
RSRAN018
RSRAN045
added, but load 5. Mobility and Handover Load Based HO Related Resources RSRAN047
5. Mobility and Handover Load Based IFHO/ISHO Performance RSRAN048
& service based 5. Mobility and Handover Load Based IFHO/ISHO Triggering RSRAN049
counters 5. Mobility and Handover Service Based IFHO/ISHO Performance RSRAN050
5. Mobility and Handover SHO Adjacencies RSRAN046
removed 5. Mobility and Handover Soft Handover Performance RSRAN028

Presentation / Author / Date

 RU10 Reporting Suite
• Modifications Report Topic Name Report Name Report ID
8. Transport ATM Interface Traffic Load RSRAN081
to KPIs due to 8. Transport ATM VCC Traffic Load RSRAN083
streaming class 8. Transport
8. Transport
ATM VPC Traffic Load
FTM Packet Transport Performance
RSRAN082
RSRAN076
+ 64 HSDPA 8. Transport
8. Transport
FTM Performance
Iu-PS Throughputs
RSRAN072
RSRAN064
users/cell 8. Transport Iub Throughputs RSRAN080
8. Transport Traffic on AAL5 RSRAN031
8. Transport Traffic on ATM Layer RSRAN029
8. Transport Traffic on Physical Medium Sub-Layer RSRAN030
8. Transport Transport Resource Reservations RSRAN069
7. HSPA Channel Switching and HSPA Layering RSRAN075
7. HSPA CQI Distribution RSRAN039
7. HSPA HSPA Code and Modulation Usage RSRAN034
7. HSPA HSPA Power Distribution RSRAN074
7. HSPA MAC-hs Efficiency RSRAN040
7. HSPA MAC-hs Retransmissions by Code and Modulation Usage RSRAN041
7. HSPA Number of HSPA Users and UE capability RSRAN051
6. Signalling NBAP Signalling RSRAN027
6. Signalling RRC Signalling RSRAN038

Presentation / Author / Date

/