3G Drive Testing & KPI

Course Outlines

• Drive Test Process

• Setup System Test
• Customer Experience KPI
• Drive Test Analysis
▪ Call Setup Failure Analysis
▪ Drop Call Analysis
Drive Test Process
 Drive Test Process

Data Preparation and

Collection
Data Analysis
•Services to test
•Levels of Reporting

Drive
Trouble Shooting
Cluster Preparation •KPI definitions
•Failure Type Breakdown •Root Cause Analysis
•Define Cluster •Equipment
•Post Processing •Corrective Action
•Define Drive Route •Exclusions
functionality •Further data logging
•Call Patterns
•KPI Gap Analysis
•OSS Alarms
•Network Stats

Why Drive the Network ?

• New Site Integration
• RF Tuning
• Network Optimisation
• Network Benchmarking (Golden clusters)
• Release Testing
Drive test Performance

There could be many reason for poor Performance, for example

• Radio Conditions
• UE Category & Performance
• Measurement tools & Settings
• Server location and settings
• HLR QoS Profile
• Network Configuration and Parameters
Setup System Test
Setup System Test – Test Equipment
• Nemo Outdoor Multi with UE’s, Scanner and GPS

Land Unit
NQMP

FTP
Server

• Important to drive with Call logging equipment and

3G and 2G scanner in the same vehicle
Setup System Test – Test Equipment, Scanner

• The purpose of using the RF scanner is to be able to scan and measure all used
carriers/cells and their corresponding DL scrambling codes.

• For low coverage areas

• For antenna installation problems
• For missing neighbours
• For coverage optimisation
• With the scanner you can get the following info from the surrounding cells:
• Different Scrambling codes
• CPCIH RSCP value (dBm)
• CPICH EcNo value (dB)
Setup System Test – Test Equipment, UE
• The Scanner measures all SCs, whereas the UE only measures SC signals from the cells that the
system has informed/ordered the UE through the BCH (neighbour list) or via the “measurement
control” message.
• RSCP Active/Monitored Set
• Carrier RSSI
• Ec/No Active/Monitored Set
• UL/DL Data Throughput
• The BLER downlink
• Pilot BER
• Random Access Initial Tx Power
• Random Access Preamble Count
• Random Access Preamble Step
• Random Access Tx Power
• SIR target (UE dependent)
• UE Tx Power
• Call Statistic: AMR, CS and PS data calls
Setup System Test – Call Patterns
• Enough call samples have to be made to make the measurement statistically valid.
• In a 50 call sample one dropped call will cause a change in performance of -2%
• In a 500 call sample one dropped call will cause a change in performance of -0.2%
• Call length should be defined at the beginning
• We can use different call testing patterns for different optimisation techniques
• Short Calls (for Calls setup performance and delay)
• Long calls (for Drop call performance and SHO performance)

AMR Call PS Call

Mobile Originated Calls (MOC) • GPRS Attach,
• 2 min calls • PDP Context Activation
• 30 sec idle • FTP Download (1MB file)/FTP Upload (500 KB file)
• UE in Dual mode (2G/3G) • PDP Context Deactivation
Mobile Terminated Calls (MTC) • GPRS Detach
• 2 min calls • Alternate download and upload with 30 sec idle time
• 30 sec idle • Session is upload or download
• UE in dual mode (2G/3G) • UE in Dual mode (2G/3G)
Customer Experience KPI
 Drive test KPI’s for CS

Drive test KPIs for CS domain – All Mobility measurements

PI # FPI Name Triggering Maximum Results Normal Results Test Setup

MOC setup time is the interval between the submission of the "RRC
Call Setup Time - Voice MOC @
FPI_6a CONNECTION REQUEST" message and the reception of the L3 2.1 sec 3.5 sec 1 UE MOC to test number:
95%
msg "CC ALERTING" at a UE.

Ratio between successfully established CS voice calls compared to

Call Setup Success Rate - Voice
FPI_7 the overall number of voice call establishment attempts - “DL direct 99% 1 UE MOC to test number:
(%)
transfer (CC: alerting)” message is received by UE

Ratio between abnormally released voice calls and the overall

FPI_9 Drop Call Rate - Voice (%) number of established voice calls (e.g. “RRC Connection Release” 1% 1 UE MOC to test number:
message is received before “UL/DL CC: disconnect” )

Call Setup Time - Voice MMC “RRC Connection request” message to “DL direct transfer (CC: 2 UE (MOC+ MTC) – from
FPI_6b 3.8 sec* 6.5 sec
(sec) alerting)” msg. moving UE to stationary
Drive test KPI’s for CS – Test Setup

Typically a few different type of call scenarios is used to measure CS KPIs.

• Call length have impact for the drop call rate, at least 90 sec call should be used to measure drop call rate. Shorter
call can be used to measure CSSR.
• Call length has no impact for the call setup times.
• ISHO measurement require dual mode UE, but for KPIs UE is typically locked.
Below some possible call scenarios that can be used to measure CS KPIs
• 90 sec call with 15 sec idle from UE to PSTN – UE locked
• Drop call rate
• MOC call setup time
• SHO success and overhead
• 30 sec call with 15 sec idle from 3G to 3G – UE locked (B-party stationary)
• CSSR (voice)
• MMC call setup time
• 30 min long call – UE in dual mode
• ISHO success
Drive test KPI’s for CS – Call setup success and Setup time

Call setup success & time is measured between RRC Connection request and Alerting
UE Node B RNC CN

RRC Connection Request (RACH)

RRC Connection Setup (FACH)

RRC Connection Setup Complete (DCH)
Initial Direct Transfer (CM Service Request)
RANAP: Initial UE msg.

DIRECT TRANSFER (CM service Accept)

Call Setup Success &
DIRECT TRANSFER (Setup) Time

DIRECT TRANSFER (Call Proceeding)

RANAP: RAB Assignment Request

RRC: Radio Bearer Setup

RRC: Radio Bearer Setup Complete

RANAP: RAB Assignment Response

DIRECT TRANSFER (Alerting)

DIRECT TRANSFER (connect)
DIRECT TRANSFER (connect Acknowledge)
 Drive Test KPIs for PS – Success and Drop ratios

Drive test KPIs for PS Domain

Maximum Normal
PI # FPI Name Triggering Test Setup
Results Results

FPI_20 Average GPRS Attach Time (sec) “RRC Connection request” message to “Attach Accept” message 1 PS MOC UE
1.5 sec 2 sec
Between the "RRC CONNECTION REQUEST" msg. and the
reception of the L3 message "ACTIVATE PDP CONTEXT
FPI_21a Average PDP Context Activation time 1 PS MOC UE
ACCEPT" at a UE.
Time for Attach not included 1.4 sec 2 sec
“RRC Connection request” message to “Activate PDP context
FPI_22 Activate PDP Context Success Rate (%) 99% 1 PS MOC UE
Accept” message
Number of successful PS setups - number of lost PS
FPI_27 PS Retainability ratio (%) 99% 1 PS MOC UE
sessions/Number of established PS sessions.
Drive Test KPIs for PS – GPRS Attach Time

GPRS Attach Time is measured between RRC Connection Request and Attach Accept
UE Node B RNC CN

RRC Connection Request (RACH)

RRC Connection Setup (FACH)

RRC Connection Setup Complete (DCH)

Initial Direct Transfer GPRS Attach Request (DCH)
RANAP: Initial UE msg.
DIRECT TRANSFER (Authentication and ciphering request)
DIRECT TRANSFER (authentication and ciphering response) PS attach time

Security mode command

Security mode complete

Downlink direct transfer: common id

Uplink Direct transfer: identity response

Downlink direct transfer: Attach Accept

Uplink Direct transfer: Attach Complete

Drive Test KPIs for PS – PDP context activation time and success

PDP Context Activation Time is measured between RRC Connection Request and Activate PDP
context Accept
UE Node B RNC CN

GPRS Attach

RRC Connection Request (RACH)

RRC Connection Setup (FACH)

PDP context activation time
RRC Connection Setup Complete (DCH) and success
Service Request
Security mode command
Security mode complete
Activate PDP context request (DCH)

RANAP: RAB Assignment Request

RRC: Radio Bearer Setup

RRC: Radio Bearer Setup Complete

RANAP: RAB Assignment Response

Measurement Control
Activate PDP Context Accept (DCH)

Call Established
Drive Test KPIs – Test Case definition Examples
Short calls to test Call
Setup Success
KPI ID Criteria Test Description Trigger Statistics Success
Rate
KPI-01 Voice 12.2 •1 MOC+ 1 MTC in the same van, •Call set-up trigger point: •Cluster_AMR_Overall_CCSR_% = Call 98%
kbps AMR 2 Ues •Party A’s UE sends 1st ‘RRC Connection Request’ Completion / Call Attempts *100
CCSR •1 call (party A to party B, party A •Call completion trigger point:
terminates the call): 15 seconds •Party A’s UE receives ‘RRC Connection Release (cause normal)’
call + 15 seconds idle. Party A to •Successful completion if:
be logged •15 sec call duration (from RRC Conn. Request to RRC Conn.
•350 calls Release)
•Party A’s UE receives ‘RRC Connection Release (cause normal)’
KPI-02 Voice DCR •1 MOC to PSTN, 1 Ue •Call Set-up trigger point: •Cluster_AMR_Overall_DCR_% = 1 - Call < 2%
•1 call: 90 seconds call + 15 •3G UE receives ‘RRC: Downlink Direct Transfer (Alerting for NZ, Completion / Set up Calls *100
seconds idle Connect Acknowledge for AU)’
•350 calls •Call completion trigger point:
•3G UE receives ‘RRC Connection Release (cause normal)’
•Successful completion if:
Long calls to test •90 sec call duration (from RRC Conn. Request to RRC Conn.
Release)
Drop call ratio •3G UE receives ‘RRC Connection Release (cause normal)’
KPI-03 Voice 3G- •1 MOC to PSTN, 1 Ue in dual •3G to 2G HO start point: •Cluster_Voice_3Gto2G_HO_Overall_SR_% = HO 98%
2G mode •UE receives ‘RRC: Handover From UTRAN Command’ Completion / HO Attempts *100
Handover •1 call: continuous call until 3G2G •3G to 2G HO completion trigger point:
(inter- & coverage border is passed •UE sends ‘Handover Complete’ to 2G BSS
intra-MSC) •50 occurrences as a minimum •Successful completion if:
•UE sends ‘Handover Complete’ to 2G BSS

…
KPI-08 PS PDP •Same as 10 •PS PDP activation trigger point: •Cluster_PDP_Context_Activation_SR_% = PDP 98%
context •350 occurrences •UE not PS attached Context Activation Completion / PDP Context
activation •UE sends 1st ‘RRC Connection Request’ Activation Attempts *100
•PS PDP activation completion trigger point:
•UE receives ‘RRC: Downlink Direct Transfer (SM: Activate PDP
Context Accept)’
•Successful completion if:
•UE receives ‘RRC: Downlink Direct Transfer (SM: Activate PDP
Context Accept)’
KPI-09 PS •Repeated FTP calls, 1 Mbyte file •Data Session Set-up trigger point: •Cluster_PS_DL_Throughput = Average 200 Kbps
throughput download, 1 Ue •UE receives 1st DL packet Throughput Over Data Sessions
downlink •384 kbps •Data Session Completion trigger point:
•Average throughput •UE receives last packet
•350 calls •Session output:
•Average downlink throughput
Drive Test Analysis
Definition of Call Set-Up Success Rate (CSSR)
UE RNC CN
BTS
RRC: Connection Request
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 Proceeding) Call Set-up
RANAP: RAB Assignment Request Success
Rate
RAB Connection Setup phase
Resource Reservation in RNC, BTS, Transmission
Call Set-up
RRC: Radio Bearer Set-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)
Successful call setup means
that “DL/UL Direct Transfer
(CC: Alerting)” message is
received by UE
Definition of the Call Completion Rate (CCR)
UE Node B RNC MGW

DIRECT TRANSFER (Alerting)

DIRECT TRANSFER (Connect)
DIRECT TRANSFER (Connect Acknowledge)
Call Established
Call Drop
Direct Transfer (Disconnect)
Direct Transfer (Release)
Rate
Direct Transfer (Release Complete)
Iu Release Command Call
Iu Release Complete Duration
RRC Connection Release
RRC Connection Release Complete
RRC Connection Release Complete
RRC Connection Release Complete
Radio Link Deletion Request
Radio Link Deletion Response
ALCAP: Release Request
ALCAP: Release Response
ALCAP: Release Request
ALCAP: Release Response

Call Released
Definition of Session Setup Time - PS
UE WBTS RNC
UE already has an RRC connection
CN
INITIAL DIRECT TRANSFER (Attach Request)
INITIAL UE MESSAGE (GPRS Attach)
SCCP: Connection Request

SCCP: Connection Confirm

Downlink Direct Transfer (Authentication & Ciphering Request) RANAP: Authentication & Ciphering Request

Uplink Direct Transfer (Authentication & Ciphering Response) RANAP: Authentication & Ciphering Response
Security Mode Command RANAP: Security Mode Command

Security Mode Command RANAP: Security Mode Command

RANAP: Common ID
Downlink Direct Transfer: Identity Request RANAP: Identity Request
Uplink Direct Transfer: Identity Response RANAP: Identity Response

Downlink Direct Transfer: Attach Accept Direct Transfer: Attach Accept Session Set-
up Time
Uplink Direct Transfer: Attach Complete Direct Transfer: Attach Complete

INITIAL DIRECT TRANSFER (Active PDP Context Request) DIRECT TRANSFER (Active PDP Context Request)
RANAP: RAB ASSIGNMENT REQUEST
RRC: Radio Bearer Set-up
RRC: Radio Bearer Set-up Complete
RANAP: RAB ASSIGNMENT RESPONSE
RRC: Measurement Control
DIRECT TRANSFER (Active PDP context Accept)
Failure Breakdown
• Non-genuine failures
• Measurement system fault (Collection Tool
or Analysis)

• Genuine failures
It is beneficial to categorise • RF issue (Coverage / Interference / Poor
call failures during the dominance)
analysis and reporting • Missing neighbour
• System issue WBTS
• System issue RNC
• Core network issue
• System
• (Unknown )

UE

Iub Iu
WBTS RNC Core NW
Failure Breakdown
• The KPI measurement conditions should be used to define exclusion areas
during drive test for acceptance of a cluster.
• All failures happening in those area, that do not respect the coverage
requirements should be discarded.

RSCP
Example of Call Success Criteria Ec/No
Signal Call
above OK
Signal above
Call Call - (B) Ec/No
RSCP Call
- 80dBm OK
NOK - 5dB threshold
threshold

- -95dBm - 12dB
Signal Signal
below below
RSCP Call Ec/No
threshold -110dBm
Threshold
OK
 Call
- 20dB threshold
Call- (A) NOK Discard sample

Time
Failure Breakdown
AMR Call Setup Failures
Call Set-up Failures Breakdown - Benchmark Drive
Call Setup Failure Breakdown - Final Drive

5% 5% Equipment 0%
0%
0%
Registration Clash
0% Equipment
15%
Core Network 19% 19% Registration Clash
20%
Fail in 2G Core Network

Fail in 2G
RAN (fixed in next release) 0%
0% RAN (fixed in next release)
Site maintenance (TMUK) 0%
Site maintenance (TMUK)
0% RAN (Other)
RAN (Other)
10%
5% Missing neighbours
Missing neighbours
0% 3G RF 3G RF
0%
0%
slow cell Reselection 0% Slow cell reselection

10% site configuration & maintenance

site configuration & maintenance
(Nokia)
35% (Nokia) Other
Other
5%
52%

Call Set-up Failures Call Set-up Failures

Call Set-up Exceptions Call Se
Failure Type total % Failure Type total %
Equipment 1 5.0 Equipment 0 0.0
Registration Clash 4 20.0 Registration Clash 0 0.0
Core Network 0 0.0 Core Network 0 0.0
Fail in 2G 1 5.0 Fail in 2G 6 19.4
RAN (fixed in next release) 0 0.0 RAN (fixed in next release) 0 0.0
Site maintenance (TMUK) 0 0.0 Site maintenance (TMUK) 16 51.6
RAN (Other) 2 10.0 RAN (Other) 0 0.0
Missing neighbours 1 5.0 Missing neighbours 0 0.0
3G RF 7 35.0 3G RF 3 9.7
slow cell Reselection 3 15.0 Slow cell reselection 0 0.0
site configuration & maintenance (Nokia) 0 0.0
site configuration & maintenance (Nokia) 0 0.0
Other 1 5.0
Other 6 19.4
Drive Survey Analysis Process Summary Diagram
Non Genuine Call Setup Failure Scenarios

• Measurement systems are often not perfect and may introduce errors in data collection
or analysis

• Examples of non-genuine failures seen:

• Uplink: CM Service Abort within milliseconds from CM Service Request

• Call attempt during Location Area update (‘LA clash’)
• User initiated “UL CC Disconnect”
• Location Area update interpreted as call setup failure
• Cell reselection back to 3G from 2G interpreted as call setup failure
Non Genuine Call Setup Failures
• Measurement system failures by drive test tool
• “CM Service Abort” within milliseconds from “CM Service
Request”
• No time for response from NW
Non Genuine Call Setup Failures
• Measurement system failures by
drive test tool
• Call attempt during Location Area
update (LA update clash)

LA Update
Request
Call attempt

RRC Release
Non Genuine Call Setup Failures
Measurement system failures by Actix workbook
• Successful or failed Location Area update interpreted as call setup failure

LA Update
Request

RRC Connection
for Inter-RAT cell
reselection
Non Genuine Drop Call Scenarios
Measurement system failure examples:
• Drive test tool
• User initiated “UL CC Disconnect”
• Analysis Workbook
• Inter-Rat cell reselection from 2G to 3G interpreted as drop call
• Complete (e.g 90 seconds) call on either 3G or 2G
• No drop in the log file / same drop listed twice
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”
Failure Location

• Analyse the
signalling flow
to find the
location of
failure and
potential cause

• UE log may only

capture some of
the messages
Call Setup Failure Start

Analysis Process A Coverage Optimization

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

Yes
UL coverage & RACH
B parameter. Optimization
(changing serving cell)
No AICH(ACK) received? Report & Finish
(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?

Yes E
Report & Finish
Check failure cause
(Not radio problem/cell update)
Call setup failures – RF issue
• RF issue? Coverage / Interference / Dominance A

See the example in Module 3 – RF Optimisation

Call setup failures – Missing Neighbour
A
• 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- Block B -
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 settings for
pre-amble transmission or open loop power control information is not correct.
• UL Coverage limit: UL coverage of UE is smaller compared to serving cells DL
coverage so that UE’s Tx power cannot reach serving cell.

• The Basic theory for RACH setup procedure and planning parameters can be found in
Module 6 – Parameter Optimisation
Call Setup Failure Analysis- Block B -
UE
Preamble/RACH
WBTS RNC B
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
Downlink
BS
Not detected
L1 ACK / AICH
B
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- Block B-

• Solutions for RACH optimisation

B
No
Max UE Tx power hit To increase PRACH_Preamble_retrans
the UE_P_MAX(24dBm)? Or PowerRampStepPRACHPreamble

Yes
Yes
Is UL Interference Report there might be an interfering
abnormally HIGH? source Nearby the serving cell

No
Change the Serving cell to cover the problem Area
=> UE is too far to reach the serving cell
Call Setup Failure Analysis- Block B
B
Open loop Power Control
parameters from RACH Info
message
Call setup failures – System issue BTS
• No response to “RRC Connection Request”
• Good RF conditions
C
• 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 – System issue BTS
• “RRC Connection Reject” after “RRC Connection Request” C
• 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 overload thresholds (PrxTarget + PrxOffset
and PtxTarget + PtxOffset) then AC can't admit more RABs to the cell
Call Setup Failure Analysis
• During the pre-optimization phase it is unlikely that AC will stop an RRC connection setup C
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 Analysis
D
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 – System issue RNC
• “CC Disconnect” after “Call
E
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 – System issue RNC
• “CC Disconnect” after “Call
Proceeding” (cont.)
E
• 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 NW
• “CM Service Abort” after “CM
Service Request”
E
• Good RF conditions
• “Security Mode Command”-
message not received by UE,
thus the failure is believed to
be at Core Network.
UE Node B RNC MGW

RRC Connection Establishment

Initial Direct Transfer (CM Service Request) SCCP: Connection Request

SCCP: Connection Confirm

Location Reporting Control
Common ID
Security Mode Command

• RRC: Initial Direct Transfer message is sent using acknowledged mode RLC to the CS core
domain. Routing is to be based upon the local P-TMSI

• The NAS message is not read by the RNC but is forwarded to the multimedia gateway. The NAS
message includes the IMSI as a UE identity
• The SCCP: Connection Request message establishes the connection orientated signalling link in
the same way as it was for the RRC connection phase.This does not reserve any resources for the
AMR call itself.
• The Connection Confirm message identifies the RNC with a destination local reference which is the
same as the source reference within the Connection Request message
• The Connection Confirm message identifies the CS core with a source local reference
• The CS core sends a RANAP: Location Reporting Control message to the RNC requesting
information regarding the location of a particular UE
• The RANAP: Common ID message 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 – System Issue (test number)
• “CC Disconnect” after “CC Progress”
• Cause: recovery on timer expiry
E
• 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 with the test
number not the RAN
30 sec

Cause: recovery on
timer expiry
 Start
Call Drop Failure Analysis Process
SHO Failure Yes
SHO Failed
Analysis
No

ISHO Failure Yes

ISHO Failed
Analysis No

No

Best server’s No
Coverage Optimization
RSCP > -102dBm

Best server’s Missing No

Dominance Optimization
Ec/No > -12dB Neighbour

A Yes Neighbour list

Optimization
Yes

Investigate
B possible BTS or
RNC problem
Call Drop Failure Analysis Process (SHO Analysis)
Start

Yes
Check Iur Inter RNC HO
Yes
Check neighbour definition parameters
No

Yes No DL ASU
Fix SC Clash SC Clash
received
C
Yes
No

Yes Congestion on
Load Optimisation
target cell
UE Tx Power Max Check RF Levels
No

DL Tx Power Max No
Yes
D
Yes Load Optimisation/
Uplink Interference
External Interferer
Yes
No

Yes
Link Unbalanced CPICH Optimisation
Drop call failures – RF issue
• RF drops mostly due to poor dominance or
interference
A
• 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 and eventually to
drop call.
Poor dominance
causes Active Set
update failures
Drop call failures – RF issue
A

DL synchronisation is lost -> UE has

stopped transmitting

TrChAgg and DL
DPCCH BER high
Drop call failures – RF issue
A
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
Drop call failures – System issue BTS
B
• Sudden drop to idle, no disconnect messaging
• Site malfunctions to be checked
• In the example below site had faulty unit (WTR)

Drop to IDLE
Drop call failures – System issue RNC
• “CC Disconnect” due to “DL
DPCCH BER B
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”
Drop call failures (SC conflict)
• Sudden drop to idle mode
(no disconnect messaging)
Transport
channel BLER
C
• Cause of the failure: 100%
overshooting site and SC
reuse
• Short term solution to add
overshooting neighbour in
ADJS definitions

Cell ABC, SC258

Drop Call - Uplink Interference
UL interference from the SIB7
message
D
Drop Call – Link Balance
• UL & DL Power Control commands can help indicating
problems in link balance.
UE RX power control message:
DL reception weak -> UE is
ordering WBTS to increase
D
• PC frequency is 1500 Hz, thus ideally the sum of PC power.
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.
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
Thank You