Coaching Session - 3G Voice Call Analysis - v04

3G Voice Call Analysis
Analysis of drive test log files
Company Confidential
1 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials
Objective
To understand the progress of a 3G voice call from the perspective of drive testing. To understand what a good call look like To understand typical failures seen in the drive test logs If times permit to look at individual issues raised by the audience. Improve ability to analyse drive test log and understand the failures NOT discussing Counters, Logging equipment, analysing tools, RNC logging.
NOT discussing Counters, Logging equipment, analysing tools, RNC logging.
Agenda
Overview of used protocols
Short introduction to Radio protocol, Iub, Iu-CS
Overview of Radio Resource Management Signalling in a normal successful call

MTC and MOC Call setup Active set update Intersystem handover Disconnect
Methods used for analysing drive test log files Examples of unsuccessful calls
Additional examples of signalling in case of failures
Protocol Stacks
Node B Uu Iub
RNC Iu,cs
Multimedia Gateway A
3G MSC
CS Core Network
Communication between UE, RNC and CS Core makes use of Uu, Iub, Iu.cs and A Interface protocols All protocols includes both user and control planes The control plane of one protocol stack may make use of the user plane of another protocol stack e.g. RRC messages which form the control plane of the radio access protocol are communicated to and from the Node B using the user plane of the Iub protocol stack
Protocol Summary
In drive test analysis two types of message are visible from the drive test log
RRC messages NAS messages note that NAS message is embedded in RRC messages
UE
NAS Messages Core
RRC Messages
RNC
Node B
NBAP Messages
SWPRB Internal Messages RANAP Messages
ALCAP Messages
SWPRB
CS Radio Interface Protocol (RIP) User Plane

The 3G MSC provides connectivity to the circuit switched core and PSTN The multimedia gateway provides transcoding for
Speech calls: between AMR and A Law PCM Video calls: no transcoding is required i.e. vocoder appears only in the UE
Transparent mode RLC is used between the UE and RNC AAL2 based ATM is used to transfer user plane data across the Iub and Iu,cs interfaces
UE
e.g. vocoder RLC-U MAC
Multimedia GW RNC
RLC-U Iu,cs UP AAL2 ATM Phy e.g. vocoder Iu,cs UP AAL2 ATM Phy A Law PCM, etc
3G MSC
A Law PCM, etc PSTN
Node B
FP AAL2
MAC FP AAL2 ATM Phy
WCDMA L1
WCDMA L1
ATM Phy
Link Layer Phy
Link Layer Phy Phy
Uu
6 2005 Nokia
Iub
V1-Filename.ppt / yyyy-mm-dd / Initials
Iu,cs
CS Radio Interface Protocol (RIP) Control Plane

The radio interface protocol control plane allows RRC signalling between the RNC and UE RRC signalling is communicated across the Iub using the Iub user plane protocol stack i.e. using Frame protocol and AAL2 based ATM Acknowledged or unacknowledged mode RLC is used between the UE and RNC
UE
RRC RLC-C MAC
RNC
RRC RLC-C
Node B
FP AAL2
MAC FP AAL2 ATM Phy
WCDMA L1
WCDMA L1
ATM Phy
Uu
Iub
Iub Protocol Stack

The Iub protocol stack has three planes The radio network control plane uses the NBAP protocol and completes tasks such as configuring a radio link at a Node B The transport network control plane uses ALCAP and is responsible for setting up and tearing down user plane transport bearers The user plane uses Frame Protocol and is responsible for encapsulating all data to and from the UE
Radio Network Control Plane NBAP Transport Network Control Plane User Plane
Frame Protocol
ALCAP Q.2630.1 Q.2150.2 SSCF-UNI SSCOP AAL5 SSCF-UNI SSCOP AAL5 ATM Physical Layer AAL2
Iu-cs Protocol Stack

The Iu-cs protocol stack has three planes The radio network control plane uses the RANAP protocol and completes tasks such as configuring a RAB or assigning Iucs resources The transport network control plane is responsible for setting up and tearing down Iu transport bearers The user plane is responsible for encapsulating all data to and from the UE
Radio Network Control Plane RANAP
Transport Network Control Plane
User Plane Iu User Plane Protocol
Q.2630.1 SCCP MTP3b SSCF-NNI SSCOP AAL5 Q.2150.1 MTP3b SSCF-NNI SSCOP AAL5 ATM Physical Layer AAL2
Radio Resource Management (RRM): Tasks

Predict the impact on interference (power) of admitting a new user for Uplink and Downlink Power Perform appropriate actions (e.g. new call admissions, bitrate increase/decrease etc.) in accordance with load conditions Provide different quality of service for real time (RT) and non-real time (NRT) users
Overload Load Target Overload Margin
Take appropriate corrective action when the different cell load thresholds are exceeded in order to maintain cell stability (i.e. load control)
Time
Estimated capacity for NRT traffic Measured load caused by non-controllable load (RT)
RT services must have higher quality assurance than NRT

Radio Resource Management (RRM): Functions

RRM is made up of a number of closely interdependent functions (i.e. algorithms) These functions can be divided into:
Power Control (PC) Handover Control (HC) Packet Scheduler (PS) Load Control (LC) Admission Control (AC) Resource Management (RM)
LC
Cell Based Connection Based
RRM
PC
HC
AC RM
PS
Radio Resource Management (RRM): Conn. based functions

Power Control (PC)
Continuously monitors the quality of the radio link and adjusts MS, BTS powers Ensures absolute minimum Tx power is used to maintain required quality Subdivided into:
Closed loop PC, Open loop PC and Outer loop PC
Handover Control (HC)

Manages the mobility of the users Ensures MS is connected to the optimal cell(s) > minimising interference Subdivided into:
Intra-frequency handovers, Inter-frequency (hard) handovers and Inter-system handovers
RRM PC HC
LC PS
AC RM
Radio Resource Management (RRM): Cell based functions

Packet Scheduler (PS)
Scheduling packets on the radio interface (UL/DL) Ensures fast allocation of resources for NRT users
Load Control (LC)

Takes care of radio network stability Gathers interference information and provides cell load status to AC & PS
Admission Control (AC)

Performs the admission control for new bearers. Predicts interference caused by the bearer and checks whether there is room for it. Power allocation Defines transport channel parameters
RRM PC HC
LC PS
AC RM
Resource Management (RM)

Manages the physical resources of RAN Maintains the code tree and code allocations
Signalling for a Successful AMR Call

Call setup
Mobile terminated call Mobile originated call NOTE: ASU is possible after RRC connection is established but not during Radio bearer setup (seen from the RNC side)
Active call
Measurement controls Measurement reports Active set updates Physical reconfigurations
Inter system handovers
Disconnect
Released by network (in drive test normally for MTC) Released by user (in drive test normally for MOC)
Mobile Terminated Call (MTC) - I

RANAP RRC RRC PAGING TYPE 1 (PCCH) RRC CONNECTION REQUEST (CCCH) RRC RRC PAGING
Core Network
RANAP
Admission Control
NBAP NBAP ALCAP ALCAP FP FP RRC RADIO LINK SETUP REQUEST RADIO LINK SETUP RESPONSE ERQ ECF Downlink Sync Uplink Sync NBAP NBAP ALCAP ALCAP FP FP
RRC CONNECTION SETUP (FACH)
RRC
L1 SYNCHRONISATION
NBAP RRC RRC SYNCH INDICATION NBAP RRC RRC
RRC CONNECTION SETUP COMPLETE (DCH) INITIAL DIRECT TRANSFER (Paging Response)
Mobile Terminated Call (MTC) - II

INITIAL UE MESSAGE RANAP
SCCP
Core Network
SCCP
RANAP
SCCP: CONNECTION REQUEST SCCP: CONNECTION CONFIRM
SCCP RANAP RANAP RRC RRC RRC RRC RRC RRC RRC RRC DIRECT TRANSFER (MM Authentication Request) DIRECT TRANSFER (MM Authentication Response) SECURITY MODE COMMAND SECURITY MODE COMMAND COMPLETE DIRECT TRANSFER: CC SETUP DIRECT TRANSFER (MM Identify Request) DIRECT TRANSFER (MM Identity Response) DIRECT TRANSFER : CC CALL CONFIRMED RRCRANAP RRCRANAP RRCRANAP RRCRANAP RRCRANAP RRCRANAP RRCRANAP RRCRANAP RANAP
SCCP
LOCATION REPORTING CONTROL RANAP COMMON ID RANAP RANAP RANAP RANAP RANAP RANAP RANAP RANAP RANAP RAB ASSIGNMENT REQUEST RANAP
Admission Control
NBAP RL RECONFIGURATION PREPARE RL RECONFIGURATION READY NBAP NBAP
NBAP
Mobile Terminated Call (MTC) - III

ALCAP ALCAP FP FP ERQ ECF Downlink Sync Uplink Sync ALCAP ALCAP FP FP ALCAP ALCAP NBAP RRC RRC RL RECONFIGURATION COMMIT NBAP RRC RRC RANAP RRC RRC RRC DIRECT TRANSFER: ALERTING DIRECT TRANSFER: CONNECT DIRECT TRANSFER: CONNECT ACKNOWLEDGE RRCRANAP RRCRANAP RRCRANAP RAB ASSIGNMENT RESPONSE ERQ ECF
Core Network
ALCAP ALCAP
RADIO BEARER SET-UP (DCCH) RADIO BEARER SET-UP COMPLETE (DCCH)
RANAP RANAP RANAP RANAP
MTC Call Established
Mobile Originated Call (MOC) - I

RRC RRC CONNECTION REQUEST (CCCH) RRC
Core Network
Admission Control
NBAP NBAP ALCAP ALCAP FP FP RRC RADIO LINK SETUP REQUEST RADIO LINK SETUP RESPONSE ERQ ECF Downlink Sync Uplink Sync NBAP NBAP ALCAP ALCAP FP FP RRC
L1 SYNCHRONISATION
NBAP RRC RRC SYNCH INDICATION NBAP RRC RRC INITIAL UE MESSAGE RANAP
SCCP
RRC CONNECTION SETUP COMPLETE INITIAL DIRECT TRANSFER (MM CM Service Request)
SCCP: CONNECTION REQUEST
SCCP
RANAP
Mobile Originated Call (MOC) - II

SCCP RANAP RANAP RRC RRC RRC RRC RRC RRC RRC RRC DIRECT TRANSFER (MM Authentication Request) DIRECT TRANSFER (MM Authentication Response) SECURITY MODE COMMAND SECURITY MODE COMMAND COMPLETE DIRECT TRANSFER: CC SETUP DIRECT TRANSFER (MM Identify Request) DIRECT TRANSFER (MM Identity Response) DIRECT TRANSFER : CC CALL PROCEEDING RRCRANAP RRCRANAP RRCRANAP RRCRANAP RRCRANAP RRCRANAP RRCRANAP RRCRANAP RANAP RAB ASSIGNMENT REQUEST SCCP: CONNECTION CONFIRM
Core Network
SCCP
LOCATION REPORTING CONTROL RANAP COMMON ID RANAP RANAP RANAP RANAP RANAP RANAP RANAP RANAP RANAP RANAP
Admission Control
NBAP NBAP RL RECONFIGURATION PREPARE RL RECONFIGURATION READY NBAP NBAP
Mobile Originated Call (MOC) - III

ALCAP ALCAP FP FP ERQ ECF Downlink Sync Uplink Sync ALCAP ALCAP FP FP ALCAP ALCAP NBAP RRC RRC RL RECONFIGURATION COMMIT NBAP RRC RRC RANAP RRC RRC RRC DIRECT TRANSFER: ALERTING DIRECT TRANSFER: CONNECT DIRECT TRANSFER: CONNECT ACKNOWLEDGE RRCRANAP RRCRANAP RRCRANAP RAB ASSIGNMENT RESPONSE ERQ ECF
Core Network
ALCAP ALCAP
RADIO BEARER SET-UP (DCCH) RADIO BEARER SET-UP COMPLETE (DCCH)
RANAP RANAP RANAP RANAP
MOC Call Established
Layer 1 Synchronisation
Once the Node B has relayed the RRC Connection Setup message it starts to transmit the downlink DPCCH. Downlink power has been computed by the admission control Layer 3 of the UE uses timer T312 (6 s) and counter threshold N312 (4) to determine whether or not the L1 synchronisation has succeeded. Both T312 and N312 were broadcast to the UE in SIB 1 On the BTS side after receiving N_INSYNC_IND synchronisation indicators the BTS sends NBAP: SYNCHRONIZATION INDICATION message to RNC after which the closed loop and outer loop PC start to control the powers
On L1: Node B receives N_INSYNC_IND indicators L1 Synchronization established BTS sends NBAP: SYNCHRONIZATION INDICATION -message RNC receives RRC Connection Setup Complete message
Timer T312 started
UE receives RRC Connection Setup message
UE receives in sync indicators on L1
Timer T312 stopped L1 Synchronization established RRC Connection Setup Complete message SENT
N312 L1 in sync indicators
Admission Control Summary

Handover Control Active state mobility control Active set information Resource information Resource request Resource Manager Radio resource information Code allocation Transport resource allocation
Iu
RAB setup/modify/release request RB information Packet Scheduler Radio resource Load scheduling information Target BLER, B ER and SIR Power Control UL Outer loop power control
Admission Control
RAB admission decision Load change estimation Producing L2 parameters Producing TFS DL power allocation
Load information
Load change information
Load Control Producing of load information
UL Admission Overview
BTS sends periodically the received UL power to the RNC PrxTotal [dBm] Noise Rise NR [dB] Over Load If measured UL (PrxTotal) load exceeds overload thresholds (PrxTarget+PrxOffset) no RABs can be admitted and NRT bitrates are reduced until PrxTotal reaches again PrxTarget OVER LOAD AREA MARGINAL LOAD AREA FEASIBLE LOAD AREA Load curve in UL Fractional load [0..1] 1 PrxTarget [dB]+ PrxOffset [dB] PrxTarget [dB] XX [dB]
RNC compares the measured received power levels against the set thresholds
Marginal Load
If measured UL (PrxTotal) load exceeds target thresholds (PrxTarget) AC can admit NRT RABs to the cell. The NRT RAB bitrate can not be increased and remains at the same level as after previous scheduling period
PrxNoise [dBm] 0
Feasible Load
In feasible load area the admission decision is based on the power rise estimate of the new RT bearer
P rx_nc + P rx_nc P rx_target

If the resulting power is still below PrxTraget the RAB is admitted In case the RAB can not be admitted it is put into the queue
DL Admission Overview
BTS sends periodically the total transmitted DL power to the RNC RNC compares the measured transmitted power levels against the thresholds If measured DL (PTxTotal) transmitted power exceeds overload thresholds (PtxTarget+PtxOffset) no RABs can be admitted and NRT bitrates are reduced until PtxTotal reaches again PtxTarget If measured DL (PtxTotal) transmitted power exceeds Marginal target thresholds (PtxTarget) AC can admit NRT RABs to the cell (no RT RABs can be admitted). The NRT Load RAB bitrates can not be increased and they remain at the same level as after previous scheduling period In feasible load area the admission decision is based Feasible on the power rise estimate of the new RT bearer Load Over Load
PtxTotal [dBm] Cell maximum [dBm] PtxTarget [dBm]+ PtxOffset [dB] OVER LOAD AREA MARGINAL LOAD AREA FEASIBLE LOAD AREA Load curve in DL
PtxTarget [dBm]
1 Load [0...1]
P tx_total + P tx P tx_target
If the resulting power is still below PtxTraget the RAB is admitted

In case the RAB can not be admitted it is put into the queue
Admission Control in RRC Request

SRNC RRM PC HC RANAP PS LC Iu UP RM NBAP FP RNSAP AC RRC PDCP RLC MAC
Admission Control in RAB Assignment

SRNC RRM PC HC RANAP PS LC Iu UP RM NBAP FP RNSAP AC RRC PDCP RLC MAC
Admission Control Functional overview
Call Disconnect
The disconnect described in the next slide are normal disconnects i.e. the UE receives (sends) a disconnect message from (to) the network
Mobile Originated Release

Active AMR Call ongoing
RRC RRC RRC DIRECT TRANSFER: CC DISCONNECT DIRECT TRANSFER: CC RELEASE DIRECT TRANSFER: CC RELEASE COMPLETE RRCRANAP RRCRANAP RRCRANAP RANAP RANAP RRC RRC RRC RRC RRC CONNECTION RELEASE (DCH) RRC CONNECTION RELEASE COMPLETE RRC CONNECTION RELEASE COMPLETE RRC CONNECTION RELEASE COMPLETE NBAP NBAP RADIO LINK DELETION REQUEST RADIO LINK DELETION RESPONSE RRC RRC RRC RRC NBAP NBAP ALCAP ALCAP ALCAP ALCAP RELEASE REQUEST RELEASE RESPONSE ALCAP ALCAP RELEASE REQUEST RELEASE RESPONSE IU RELEASE COMMAND IU RELEASE COMPLETE
Core Network
RANAP RANAP RANAP RANAP RANAP
ALCAP ALCAP
The Call and all resources are released

Mobile Terminated Release

RRC RRC RRC DIRECT TRANSFER: CC DISCONNECT DIRECT TRANSFER: CC RELEASE DIRECT TRANSFER: CC RELEASE COMPLETE RRCRANAP RRCRANAP RRCRANAP RANAP RANAP RRC RRC RRC RRC RRC CONNECTION RELEASE (DCH) RRC CONNECTION RELEASE COMPLETE RRC CONNECTION RELEASE COMPLETE RRC CONNECTION RELEASE COMPLETE NBAP NBAP RADIO LINK DELETION REQUEST RADIO LINK DELETION RESPONSE RRC RRC RRC RRC NBAP NBAP ALCAP ALCAP ALCAP ALCAP RELEASE REQUEST RELEASE RESPONSE ALCAP ALCAP RELEASE REQUEST RELEASE RESPONSE IU RELEASE COMMAND IU RELEASE COMPLETE
Core Network
ALCAP ALCAP
The Call and all resources are released

Active Set Update

The active set update (or soft/softer handover) is decided upon by the RNC based on the measurement reports received from the UE. Exactly how the trigger mechanism works depend on if the UE is in a Nokia or Nortel area but the final result should be the same, namely adding, replacing or deleting one or more cells from the active set. Only Addition is shown Signalling is slightly different for different case but only one is shown here. The possible cases are
Intra RNC Softer Handover (HO between cells under the same WBTS) Intra RNC Soft Handover (HO between cells in different WBTS) Inter RNC Soft Handover (HO between cells in WBTS in different RNCs)
Reporting event 1A: A Primary CPICH Enters the Reporting Range

ActiveSetWeightingCoefficient
Strongest CPICH in AS Ec/Io P CPICH 2 P CPICH 1
AdditionWindow
1 2
P CPICH 3 time 3
AdditionTime
Measurement Report no Add to the AS?
AdditionReportingInterval
RNC
Reporting event 1B: A Primary CPICH Leaves the Reporting Range

Ec/Io Strongest CPICH in AS P CPICH 1 P CPICH 2 1 P CPICH 3 2
DropWindow
3 time
DropTime
Measurement Report
Remove the reported cell from the AS
Reporting event 1C: A non-active CPICH becomes better than an active primary CPICH
AS has 3 cells Ec/Io P CPICH 1 P CPICH 2 1 P CPICH 4
ReplacementWindow
P CPICH 3
weakest CPICH3 in AS
time 2
ReplacementTime
Measurement Report
ReplacementReportingInterval
no AS update?
RNC
Cell 1
Cell 2
ACTIVE SET UPDATE Addition A-I

Core Network
RRC RRC
MEASUREMENT CONTROL MEASUREMENT REPORT (DCCH): e1a
RRC RRC
Handover Control Admission Control

NBAP NBAP ALCAP ALCAP FP FP RADIO LINK ADDITION REQUEST RADIO LINK ADDITION RESPONSE ERQ ECF Downlink Sync Uplink Sync NBAP NBAP ALCAP ALCAP FP FP Required for soft handover
Cell starts receiving

NBAP SYNCH INDICATION NBAP Required for soft handover
Cell starts transmitting Company Confidential

Cell 1
Cell 2
ACTIVE SET UPDATE Addition A-II
Core Network
RRC RRC
ACTIVE SET UPDATE
RRC RRC
RRC RRC RRC RRC RRC RRC
ACTIVE SET UPDATE COMPLETE
RRC RRC
MEASUREMENT CONTROL
RRC RRC
MEASUREMENT CONTROL
RRC RRC
New Cell has been Added and Neighbour lists are updated
Cell 1
Cell 2
ACTIVE SET UPDATE Addition B-I

MEASUREMENT REPORT (DCCH): e1a
DRNC
SRNC
RRC
RRC
Handover Control Admission Control

RNSAP BRANCH ADDITION REQUEST RNSAP
Admission Control
NBAP NBAP ALCAP ALCAP FP FP RADIO LINK SETUP REQUEST RADIO LINK SETUP RESPONSE ERQ ECF Downlink Sync Uplink Sync NBAP NBAP ALCAP ALCAP FP FP RNSAP ALCAP ALCAP BRANCH ADDITION PROCEEDING RNSAP ERQ ECF ALCAP ALCAP Required for soft handover
Cell starts receiving
Cell 1
Cell 2
ACTIVE SET UPDATE Addition B-II

ACTIVE SET UPDATE (DCCH)
DRNC
SRNC
RRC
RRC
L1 SYNCHRONISATION
NBAP SYNCH INDICATION NBAP Required for soft handover
Cell starts transmitting

RRC ACTIVE SET UPDATE COMPLETE (DCH) RNSAP RRC RRC MEASUREMENT CONTROL MEASUREMENT CONTROL BRANCH ADDITION COMPLETE RRC RNSAP RRC RRC
New Cell is now added to the active set
Admission Control for SHO
Inter System Handover

As for active set updates, the trigger mechanism for ISHO depends on if the network is Nokia or Nortel. The following pages describes the signalling based on the event driven mechanism, i.e. Nokia.
Inter System Handover: Procedure

HO Triggering Thresholds set in RNC HO Triggering Thresholds set in RNC Event Triggered Coverage/Capacity Event Triggered Coverage/Capacity based HO fulfilled in RNC based HO fulfilled in RNC RNC commands selected UE(s) to start RNC commands selected UE(s) to start IS measurements IS measurements Measurements are done in Measurements are done in Compressed Mode (CM) Compressed Mode (CM) UE reports GSM cells with UE reports GSM cells with strongest RSSI signals to RNC strongest RSSI signals to RNC RSSI measurements and BSIC RSSI measurements and BSIC verification for GSM cells verification for GSM cells RNC makes HO decision and RNC makes HO decision and commands UE to target cell commands UE to target cell
About 25 HO parameters E.g. event1f (RSCP or EcN0) 5 Coverage/Capacity reason: TxPwrDL, TxPwrUL, CPICH/RSCP, CPICH/EcN0, ULQuality Physical Channel Reconfiguration Msg Compressed mode needed to have time for the IS measurements More than one measurement report Only one cell Handover to GSM
Reporting events 1E and 1F: CPICH RSCP or CPICH EcN0

Reporting event: 1E: A P-CPICH exceeds an absolute threshold (triggered if one) 1F: A P-CPICH falls below an absolute threshold (triggered if all)
e.g. P-CPICH Rscp Cell 1 Cell 2
Cell 3 1E: HHoRscpCancel
1E: HHoRscpCancelTime
time 1F: HHoRscpTimeHysteresis
Reporting events 6A, 6B and 6D: UE Tx power

UE Tx Power
6A: The UE Tx power exceeds an absolute threshold 6B: The UE Tx power falls below an absolute threshold 6D: The UE Tx power reaches its maximum value 6D
min(UEtxPowerMaxDPCH, P_MAX)
UE Transmitted Power Tx Threshold
6A 6B
InterfreqUETxPwrTimeHyst GSMUETxPwrTimeHyst Company Confidential

time to trigger
time
Compressed Mode (CM)

CM was introduced to WCDMA to allow inter-frequency (system) handovers CM is used to create idle periods (gaps) in the transmission during which cell measurements on another frequency can be made Power / Data Rate
Normal frame Compressed Mode Normal frame Measurement gap Measurement gap Normal frame
Gaps can be created using single or double frame approach Because same data amount is sent in a shorter time more power is needed during CM (both in UE and BTS)
=> affects WCDMA coverage
Fast Power control information might be lost during the gap => higher Eb/No
=> affects WCDMA capacity
Compressed frames may be lost if power control is not set correctly

=> affects WCDMA quality
CM methods are Puncturing, Spreading Factor Halving and Higher Layer Scheduling
Maximum duration of measurements

The duration of the maximum compressed mode duration time for each GSM RSSI and BSIC decoding measurement process in seconds is given by:
(7 s) (10 reports) (0.5 s)
max_meas_interval (s) = GsmMaxMeasPeriod x GsmMeasRepInterval + 4 x GsmMeasRepInterval Gsm measurement (both RxLev and BSIC verif.) is stopped by expiration of above window. The ISHO procedure is considered to be unsucc and a new one can be activated after GsmMinMeasInterval (2s) provided that RNC does not receive a cancellation event
Inter System Handover - I

RRC Reporting event 1f triggers for first Cell in Active set RRC MEASUREMENT REPORT (DCCH): Event 1f for first cell in Active Set RRC ISHO triggering (5 reasons are possible) RRC MEASUREMENT CONTROL (DCCH) RRC
Core Network
Reporting event 1f triggers for last Cell in Active set RRC MEASUREMENT REPORT (DCCH): Event 1f for last cell in Active Set
Decision to activate inter-RAT measurements. Determination of CM-pattern NBAP NBAP NBAP RRC RRC RL RECONFIGURATION PREPARE RL RECONFIGURATION READY RL RECONFIGURATION COMIT NBAP NBAP NBAP RRC RRC NBAP RRC RRC RRC GSM RSSI Measurement Initial Compressed Mode Configuration
PHYSICAL CHANNEL RECONFIGURATION (DCCH) PHYSICAL CHANNEL RECONFIGURATION COMPLETE (DCCH) NBAP COMPRESSED MODE COMMAND (CFN, TGPSI2)
RRC RRC RRC
MEASUREMENT CONTROL (DCCH): BSIC, CFN, TGPSI2 MEASUREMENT REPORT (DCCH): GSM RSSI, BCCH ARFCN MEASUREMENT REPORT (DCCH): GSM RSSI, BCCH ARFCN
Inter System Handover - II

NBAP COMPRESSED MODE COMMAND (CFN, TGSPI3) NBAP
BSC A - Interface
GSM BSIC Identification
Core Core Network Network
RRC RRC
MEASUREMENT CONTROL (DCCH): BSIC, CFN, TGPSI3 MEASUREMENT REPORT (DCCH): BSIC, GSM Cell index)
RRC RRC BSSMAP RANAP BSSMAP RANAP
Handover Request RELOCATION REQUIRED Handover Request Acknowledge RELOCATION COMMAND
BSSMAP RANAP BSSMAP RANAP
RRC RIL3-RR
HANDOVER FROM UTRAN COMMAND Handover Access
RRC RIL3-RR RANAP BSSMAP RANAP RIL3-RR BSSMAP NBAP NBAP ALCAP ALCAP RELEASE REQUEST RELEASE RESPONSE ALCAP ALCAP IU RELEASE COMMAND Handover Detect IU RELEASE COMPLETE Handover Complete RANAP BSSMAP RANAP BSSMAP
RIL3-RR
Handover Complete NBAP NBAP RADIO LINK DELETION REQUEST RADIO LINK DELETION RESPONSE
ALCAP ALCAP
RELEASE REQUEST RELEASE RESPONSE
ALCAP ALCAP
UE is now on 2G and 3G resources have been released

Location Update
Location Update does not occur during an AMR call but since it is sometimes conflicting with the AMR call setup the signalling flow for the Location update is described in the next pages.
Location Update I
CSCore Network
Admission Control
NBAP NBAP ALCAP ALCAP FP FP RRC RADIO LINK SETUP REQUEST RADIO LINK SETUP RESPONSE ERQ ECF Downlink Sync Uplink Sync NBAP NBAP ALCAP ALCAP FP FP RRC
L1 SYNCHRONISATION
SCCP SCCP
RRC CONNECTION SETUP COMPLETE INITIAL DIRECT TRANSFER (MM LOCATION UPDATE)
RANAP
SCCP
SCCP
Location Update II
RRC RRC RRC RRC RRC RRC RRC DIRECT TRANSFER (MM Authentication Request) DIRECT TRANSFER (MM Authentication Response) SECURITY MODE COMMAND SECURITY MODE COMMAND COMPLETE DIRECT TRANSFER (MM Identify Request) DIRECT TRANSFER (MM Identity Response) DIRECT TRANSFER :LOCATION UPDATE ACCEPT RRCRANAP RRCRANAP RRCRANAP RRCRANAP RRCRANAP RRCRANAP RRCRANAP RANAP RRC RRC RRC RRC RRC CONNECTION RELEASE (DCH) RRC CONNECTION RELEASE COMPLETE RRC CONNECTION RELEASE COMPLETE RRC CONNECTION RELEASE COMPLETE NBAP NBAP ALCAP ALCAP RADIO LINK DELETION REQUEST RADIO LINK DELETION RESPONSE RELEASE REQUEST RELEASE RESPONSE RRC RRC RRC RRC NBAP NBAP ALCAP ALCAP IU RELEASE COMPLETE
Core Network
RANAP RANAP RANAP RANAP RANAP RANAP RANAP RANAP
Inter RAT Cell reselection

Qsearch_I and Qsearch_P define thresholds. The threshold value also indicates, when the measurements have to be initiated and performed. The measurements are either started, when the serving cells RLA is below or above the threshold value. The default value is 15. FDD_Qoffset and FDD_GPRS_Offset define offset values, which have to be added to the RLA of the serving and non-serving GSM cells. The result is compared with the RSCP value of the WCDMA cell. The default parameter is 0. FDD_Qmin defines a minimum CPICH Ec/No threshold for WCDMA cell for cell reselection. FDD_REP_QUANT defines the reporting quantity for UTRAN cell (1=Ec/No or 0=RSCP, default: 1). 3G_Search_PRIO is used to inidicate to the MS if 3G cells can be looked for when BSIC decoding is required. (0=no, 1=yes, default: 1)
Parameter mapping
QSearch_I/P
Fdd_Qmin
Fdd_Qmin mapping Aif parameter 0 1 2 3 4 5 6 7 Fdd_Qmin (old) [dB] -20 -19 -18 -17 -16 -15 -14 -13 Fdd_Qmin (new) [dB] -20 -6 -18 -8 -16 -10 -14 -12
New mapping from 05.08 [late 2003]: UEs have to support new parameter range !
Inter RAT Cell reselection I

PS Core Network
CS Core Network
Admission Control RADIO LINK SETUP

RRC RRC CONNECTION SETUP (FACH) RRC
L1 SYNCHRONISATION
SCCP SCCP
RRC CONNECTION SETUP COMPLETE INITIAL DIRECT TRANSFER (MM LOCATION UPDATE)
RANAP
SCCP RRC INITIAL DIRECT TRANSFER (GPRS MM ROUTING AREA UPDATE REQUEST) RRC RANAP
SCCP
INITIAL UE MESSAGE
SCCP SCCP
RANAP
SCCP: CONNECTION REQ SCCP: CONN. CONFIRM SCCP SCCP
Inter RAT Cell reselection I

RRC RRC RRC RRC DIRECT TRANSFER (MM Authentication Request) DIRECT TRANSFER (GPRS MM Authentication and Ciphering Request) DIRECT TRANSFER (GPRS MM Authentication and Ciphering Response) DIRECT TRANSFER (MM Authentication Response) RRCRANAP RRCRANAP RRCRANAP RRCRANAP
PS Core Network
CS Core Network
RANAP
RANAP RANAP RANAP
RRC RRC RRC RRC
DIRECT TRANSFER : MM Location Update Accept DIRECT TRANSFER :MM TMSI Reallocation Complete DIRECT TRANSFER : GPRS MM Routing Area Update Accept DIRECT TRANSFER : GPRS MM Routing Area Update Complete
RRCRANAP RRCRANAP RRCRANAP RRCRANAP RANAP RANAP RANAP RANAP IU RELEASE COMPLETE IU RELEASE COMPLETE RANAP
RANAP RANAP
RANAP
RRC RRC RRC RRC
RRC CONNECTION RELEASE (DCH) RRC CONNECTION RELEASE COMPLETE RRC CONNECTION RELEASE COMPLETE RRC CONNECTION RELEASE COMPLETE
RRC RRC RRC RRC
RADIO LINK DELETION Company Confidential

Methods used while analysing the log files

Analysing/opening the drive test log file (e.g. ASCOM, TEMS, Actix) Analyse current network configuration (Sites, adjacencies etc) Access to network configuration information Analysis counter metrics
Use of more than one approach is not forbidden

Summary: A 3G Voice Call Setup Phase for MTC

ASU is possible after RRC connection is established but not during Radio bearer setup (seen from the RNC side)
RRC RRC RRC RRC RRC RRC RRC RRC RRC RRC RRC RRC RRC RRC
PAGING TYPE 1 (PCCH) RRC CONNECTION REQUEST (CCCH) RRC CONNECTION SETUP (FACH) RRC CONNECTION SETUP COMPLETE (DCH) INITIAL DIRECT TRANSFER (Paging Response) SECURITY MODE COMMAND SECURITY MODE COMMAND COMPLETE DIRECT TRANSFER: CC SETUP DIRECT TRANSFER : CC CALL CONFIRMED RADIO BEARER SET-UP (DCCH) RADIO BEARER SET-UP COMPLETE (DCCH) DIRECT TRANSFER: ALERTING DIRECT TRANSFER: CONNECT DIRECT TRANSFER: CONNECT ACKNOWLEDGE
RRC RRC RRC RRC RRC RRCRANAP RRCRANAP RRCRANAP RRCRANAP RRC RRC RRCRANAP RRCRANAP RRCRANAP
Summary: A 3G Voice Call Setup Phase for MOC

ASU is possible after RRC connection is established but not during Radio bearer setup (seen from the RNC side)
RRC RRC RRC RRC RRC RRC RRC RRC RRC RRC RRC RRC RRC
RRC CONNECTION REQUEST (CCCH) RRC CONNECTION SETUP (FACH) RRC CONNECTION SETUP COMPLETE (DCH) INITIAL DIRECT TRANSFER (MM CM Service Request) SECURITY MODE COMMAND SECURITY MODE COMMAND COMPLETE DIRECT TRANSFER: CC SETUP DIRECT TRANSFER : CC CALL PROCEEDING RADIO BEARER SET-UP (DCCH) RADIO BEARER SET-UP COMPLETE (DCCH) DIRECT TRANSFER: ALERTING DIRECT TRANSFER: CONNECT DIRECT TRANSFER: CONNECT ACKNOWLEDGE
RRC RRC RRC RRC RRCRANAP RRCRANAP RRCRANAP RRCRANAP RRC RRC RRCRANAP RRCRANAP RRCRANAP
A 3G Voice Call Active Phase and Disconnect

Measurement reports
Event driven in Nokia Periodic in Nortel
Active set updates

Additions Removals Replacements
Intersystem Handovers
Compressed mode trigger GSM measurements ISHO Command Success?
Disconnection (Unexpected)
Disconnected by the network? Disconnected by the user?
Typical failures
Missing message (e.g. no L3 messages for several minutes) Cell reserved (Not seen for a while but it is an easy check) Collision between LAC update/Registration and Call attempt Call failures because of user busy (MOC) Calls disconnected by measurements system Calls disconnected by the network Missing radio bearer setup message Missing adjacencies leading to a call failure or a dropped call Poor coverage/quality
Coverage related (poor RSCP/EcN0) Quality related (poor EcN0/good RSCP)
Cells covering unwanted areas

Overshooting cells Large back loops for some cells
Have in MIND
What you see is only as seen from the UE perspective Not RNC logs What you see in the log file is not necessarily all of what the phone would be seeing
This is especially the case when evaluating the RSCP and EcN0 values.
In the following examples references are given to ASCOM, TEMS, COUEI, QVP, ACTIX etc. but most of the examples can most likely be observed in several of the tools.
Typical failures
Missing message (e.g. no RRC messages for several minutes) Cell reserved (Not seen for a while but it is an easy check in Actix) Collision between LAC update/Registration and Call attempt Call failures because of user busy (MOC) Calls disconnected by measurements system Calls disconnected by the network Missing radio bearer setup message Missing adjacencies leading to a call failure or a dropped call Poor coverage/quality

Missing messages (I)

Three types of cases
No L3 messages at all Most L3 messages are available but specific messages are missing Most L3 messages are available but now and then a single message is missing
Can happen in any part of call. When no L3 messages is seen for a long period of time it is in most case due to measurement system failure and often the final result is a restart of the measurement system (and phone). (seen with ASCOM) If the same L3 message is missing again and again this can be due to the import function of the analysing tool (seen with Actix) When a single message is missing here and there is no big problem. E.g. it can be that the radio bearer setup message is missing while the Radio bearer setup complete is in the log file. Mainly a problem for automated scripts used to identify failed/dropped calls.
Missing messages (II)

In general missing L3 messages is not a cause for a dropped or failed call but since we use automated scripts/tools, calls might be wrongly identified as failed or dropped. One type often seen is that there are no L3 messages for several min and in the internal messages a Receive inband measurements is seen. After a while the phone is then reset by the measurement system (ASCOM).
Missing messages (III): MOC Drop Call (08:23:55:080)

No L3 message for >1min and the Receive Inband measurement case!! Phone is reset by measurement system
Thursday Mar 23rd

Typical failures
Missing message (e.g. no L3 messages for several minutes) Cell reserved (Not seen for a while but it is an easy check) Collision between LAC update/Registration and Call attempt Call failures because of user busy (MOC) Calls disconnected by measurements system Calls disconnected by the network Missing radio bearer setup message Missing adjacencies leading to a call failure or a dropped call Poor coverage/quality

Cell reserved (I)

If the parameter cell reserved is set to Operator use only only specific simcards will be allowed to camp in the given cell Impact of wrong setting is general that the UE can not camp on the 3G cell and calls will therefore be made either on 2G cells or second best 3G cells. Previously a big problem with wrong settings in the network Today only cells that should actually have it set will have it set? Check the parameter setting from the SysInfo Type 3 message In Actix it is very fast to make a plot of the settings and identify cells with the special setting. Note that this is just to check if there could be a problem. The real check of this parameter should be done on the network configuration database since in the drive test the SysInfo Type 3 will only be logged for a subset of the cells located along the route (the cell passed in idle mode!) Also have in mind that in most tools all parameters send to the phone can be analysed from the logged messages
Cell reserved (II) Example

Monday Nov 7th O2 07921495158 Cell Reserved information from SysInfoType 3 message
For this drive test is seems as there where only a problem around Heathrow..
O2_0711_M11_Slough-Uu_Tec hnology _Mode (N/A ) UMTS Mode (184586) GSM mode (23511) O2_0711_M11_Slough-Uu_RRC_CellA c c es s Res tric tion_c ellRes erv edForOperatorUs e (no units )
Company erv ed (5) ( RRC_resConfidential ( RRC_notRes erv ed (634) / yyyy-mm-dd / Initials 67 2005 Nokia V1-Filename.ppt
Monday Nov 7th
Typical failures
Missing message (e.g. no L3 messages for several minutes) Cell reserved (Not seen for a while but it is an easy check in Actix) Collision between LAC update/Registration and Call attempt Call failures because of user busy (MOC) Calls disconnected by measurements system Calls disconnected by the network Missing radio bearer setup message Missing adjacencies leading to a call failure or a dropped call Poor coverage/quality

Collision between LAC update/Registration and Call attempt

Two types of collisions are seen
The UE is not registered with the network when it sends the RRC connection request The UE sets up the voice call while it is in the process of doing a registration/LU
First case leads to a rejection by the network (IMSI Unknown in network) Second case results in a failed call somewhere in the setup phase
The problem can be seen in the log file as if one RRC connection is used for both the LU and the call and when the LU is finished the RRC connection is disconnected resulting in the failed/dropped call. Often the RRC connection cause is Registration indicating that there is a collision because we are looking at a call failure.
Next couple of slide shows very brief examples of these two cases
Signalling in case of unknown IMSI

Core Network

L1 SYNCHRONISATION
RRC RRC RRC CONNECTION SETUP COMPLETE INITIAL DIRECT TRANSFER (MM CM Service Request) RRC RRC RANAP DIRECT TRANSFER (MM Identify Request) DIRECT TRANSFER (MM Identity Response) DIRECT TRANSFER : CM SERVICE REJECT (cause: IMSI unknown in VLR (Hex 04) RRC CONNECTION RELEASE (DCH) RRC CONNECTION RELEASE COMPLETE RRC CONNECTION RELEASE COMPLETE RRC CONNECTION RELEASE COMPLETE
SCCP
INITIAL UE MESSAGE SCCP: CONNECTION REQUEST

SCCP
RANAP
RRC RRC RRC RRC RRC RRC RRC
RRCRANAP RRCRANAP RRCRANAP RRC RRC RRC RRC
RANAP RANAP RANAP
Note only messages seen in log is shown
MOC Failed Call (07:59:09:420)

3 RRC ConnectionRequest (8:59:09:420, 8:59:11.530 and 8:59:12.620) before answer from network Then call is rejected due to IMSI unknown in VLR (Hex 04) Right after a registration takes place so it seems that the call fails due to missing registration.
Friday Dec 16th

MTC Failed Call (11:50:38:340)

Paging to mobile at 11:50:36:510 on SC 482 (RNC 63). Cell reselection from 482 to 315 in RNC 65 UE sets up RRC connection for call on SC 315 but then sends both a request for Registration and a paging response. When LU is finished, the RRC connection is disconnected resulting in a failed call.
Tuesday Feb 28th

Typical failures

Call failures because of user busy (MOC)

Seen as a disconnect after the radio bearer setup complete with cause user busy Exact reason is unknown but e.g. out of sync between the two phones could cause this problem Example of signalling is shown on the next two pages. In general this type of failure is identified by the rejection cause in the disconnect message.
USER BUSY I
Core Network

L1 SYNCHRONISATION
RRC RRC RRC CONNECTION SETUP COMPLETE INITIAL DIRECT TRANSFER (MM CM Service Request) RRC RRC RANAP RRC RRC RRC RRC SECURITY MODE COMMAND SECURITY MODE COMMAND COMPLETE DIRECT TRANSFER: CC SETUP DIRECT TRANSFER : CC CALL PROCEEDING
SCCP

SCCP
RRCRANAP RRCRANAP RRCRANAP RRCRANAP RANAP RAB ASSIGNMENT REQUEST
RANAP
Admission Control RADIO LINK RECONFIGURATION Company Confidential

Note that only messages relevant for log is shown
USER BUSY II
RRC RRC RADIO BEARER SET-UP (DCCH) RADIO BEARER SET-UP COMPLETE (DCCH) RRC RRC RANAP RRC RRC RRC DIRECT TRANSFER: CC DISCONNECT DIRECT TRANSFER: CC RELEASE DIRECT TRANSFER: CC RELEASE COMPLETE RRCRANAP RRCRANAP RRCRANAP RANAP RANAP RRC RRC RRC RRC RRC CONNECTION RELEASE (DCH) RRC CONNECTION RELEASE COMPLETE RRC CONNECTION RELEASE COMPLETE RRC CONNECTION RELEASE COMPLETE RRC RRC RRC RRC IU RELEASE COMMAND IU RELEASE COMPLETE RAB ASSIGNMENT RESPONSE
Core Network
RANAP RANAP RANAP RANAP RANAP RANAP
RADIO LINK DELETION
Typical failures

Calls disconnected/failed by measurement system

Causes for these failures/drops can be:
UE is reset by the measurement system UE is reset by the user The measurements are stopped
Either by drive tester Or by the measurement system itself
For ASCOM files these types of failures are often seen when there are lots of log files e.g. the number of log files for the Slough M11 route is normally 1 to 2 files but sometimes 5+ (up to 15/20 files) are seen. The problem can occur in any part of the call and in the log file it is seen as sudden loss of messages and information about restart of measurement and/or phone in the internal messages.
Typical failures

Calls disconnected by the network

Calls are seen to be disconnected from the network side There can be several reasons for this
Core network problems UL Radio problems Transmission problems Etc.
Often it is not easy to identify based on the UE logs alone why the call were disconnected by the network Next couple of slides show one example with no explanation and one with a possible explanation Generally more investigation of the cell(s)/site(s) involved is needed
RRC Disconnected by Network

Established Call
Core Network

RRC RRC RRC RRC

RRC CONNECTION RELEASE (DCH) RRC CONNECTION RELEASE COMPLETE RRC CONNECTION RELEASE COMPLETE RRC CONNECTION RELEASE COMPLETE RRC RRC RRC RRC
Note only messages seen in log are shown

Network Disconnect Example: MOC Dropped Call (12:35:30:880)
Disconnected by Network SC 368 and SC 362 in AS at time of disconnect right after an ASU to remove 369.
Monday Mar 20th

Network Disconnect Example: MOC Drop Call (11:45:21:750)

SC 11 and 258 in AS Call is released less than a second after the RB setup complete Unknown reason for release. Check uplink performance of this involved cells
Friday Mar 24th

Typical failures

Missing radio bearer setup message

Call setup gets to
-> Downlink direct transfer Call Proceeding (MOC) -> Downlink direct transfer Call confirmed (MTC) Then one or more measurement report might be seen before the UE switches to idle mode.
No radio bearer message is seen by the UE and the call disconnects Two different scenarios seen
Radio environment is poor (EcN0 and RSCP) Radio environment is good but BER deteriorates very fast to >50%
The first case is generally a question of coverage/interference or perhaps a missing adjacency The second case is still under investigation (occurs often in Nokia area) and seems to be cause by that the radio link synchronisation is lost during the Radio bearer setup (message is sent from RNC to Node B).
Missing Radio Bearer Setup - I

Core Network
Admission Control
RADIO LINK SETUP

L1 SYNCHRONISATION
RRC RRC RRC CONNECTION SETUP COMPLETE INITIAL DIRECT TRANSFER (MM CM Service Request) RRC RRC RANAP RRC RRC RRC RRC SECURITY MODE COMMAND SECURITY MODE COMMAND COMPLETE DIRECT TRANSFER: CC SETUP DIRECT TRANSFER : CC CALL PROCEEDING
SCCP

SCCP
RRCRANAP RRCRANAP RRCRANAP RRCRANAP RANAP RAB ASSIGNMENT REQUEST
RANAP
Admission Control RADIO LINK RECONFIGURATION

RRC RRC RADIO BEARER SET-UP (DCCH) MEASUREMENT REPORT (DCCH) RRC RRC
Typical failures

Missing adjacencies leading to a call failure or a dropped call

Since ASU can take place in the call setup phase missing adjacencies can give problems in both setup and active phase It can sometimes be difficult based solely on the log files to determine if the failure/drop is caused by a missing adjacency (having scanner data helps a lot in these cases) Following slides shows 7 examples of missing adjacencies identified over the last 6 months. Majority causes dropped calls. Mainly because the time spent in setup phase is smaller so less chance of experience the problem of a missing adjacency and also because the available information (not having scanner data) in the setup phase is limited so it might be more difficult to identify a missing adjacency in that phase.
Missing ADJ Ex 1: MOC Dropped Call (10:58:14:010)

Call is started at SC 345 (CellId 21704, RNC 63) at RSCP/EcN0 of -59/-4 EcN0 drops slowly to about -12 dB and then it drops rapidly to -22 dB E1a for SC 108 happens just before the value of -22 is seen. But looks like SC 109 (among others) is missing from the neighbour list!!
1411_O2_Slough_M11-Uu_Tec hnology _Mode (N/A ) UMTS Mode (206664) GSM mode (21221) 1411_O2_Slough_M11-CPICH_A llSets _UE_Ec No_For_SC_345 (dB)
Monday Nov 14th

( ( ( ( ( ( (
Below -18.0 (10) >= -18.0 to < -15.0 (5) >= -15.0 to < -13.0 (0) >= -13.0 to < -11.0 (4) >= -11.0 to < -9.0 (11) >= -9.0 to < -7.0 (2) A bov e -7.0 (40)

It does look like SC is missing a couple of neighbours. It does also look as if the whole neighbourplan of this sector (and perhaps site) should be revisisted) Note that the shown ADJS data is up to 2 weeks old
168 170 169 328 330 329 109 107 108
440 88 90 89 346 345 304 306 305 344
187
77 75 76
160 162 161
117
115
116 400
339 341 340 154 152 153
42 40 41
402
401
24 29
Monday Nov 14th


Call is started at SC 306 (CellId 31836, RNC 63) at RSCP/EcN0 of -59/-4 UE changes to SC 305 (after having both 305 and 306 in AS) EcN0 drops fast to about -24 Problem is missing ADJS (see next slide for ADJS). SC 346 is obviously missing while a few other should be added as well.
1511_O2_M11_Slough-Uu_Tec hnology _Mode (N/A ) UMTS Mode (197377) GSM mode (52468) 1511_O2_M11_Slough-CPICH_A llSets _UE_Ec No_For_SC_305 (dB)
Tuesday Nov 15th

( ( ( ( ( ( (

409 216 32
440 59 0 88 90 89 346 345 304 306 305 344
187 168 170 169 328 330 329 109 107 108
77 75 76
160 162 161
117
115
116 40
339 154 152
42 40 41
402
Tuesday Nov 15th

340
153
Missing ADJ Ex 3: MTC Failed Call (09:21:35:650)

Cell is initiated on SC 216 (CellId 11484). SC 217 is added to the AS Call fail due to missing ADJS. MR with event e1a is send for SC 203 but this SC points away from the scene and the EcN0 of SC216 and SC217 is already very low when this happens Sites neighbour planning should be revisited. For details on the ADJS see following slide. SC 205 seems to one of the missing ADJS for SC216 and perhaps SC 217
Wednesday Nov 16th

Missing ADJ Ex 3: MTC Failed Call (09:21:35:650)

319 318
319 318
9
218 216 205 217 203
218 123
216 205 203

123
217 125 124 204

125 124
204
392
392
393
224 226
393
224 226
225 35 37 36
225 35 37 36
136 137
250 248
136 137
250 248
138
249 165 163
138
249 165 163
164 434
434
164 432 349 338 336
432 349
338
336
336
336
ADJS (blue) of SC 216 (red) Wednesday Nov 16th

ADJS (blue) of SC 217 (red)
Missing ADJ Ex 4: MTC Dropped Call (10:33:35:770)
Failed ISHO: Mobile goes into Compressed mode twice. Second time the mobile send several MR with verified BSIC but there are no reply with ISHO command. At this point the EcN0 is very poor (24dB) There are 2 failed CM and several unanswered MR e1a (due to the very poor quality towards the end of the call). Coverage/quality problem missing 2G neighbours? Note: Blue star correspond to a Physical reconfiguration command triggered by poor EcN0
1611_O2_Slough_M11-Uu_Tec hnology _Mode (N/A ) UMTS Mode (157710) GSM mode (64902) 1611_O2_Slough_M11-A SCOM_CELL_RESELECTION (no units )
Wednesday Nov 16th

( ( (
3G->2G CR (7) 2G->3G CR (34) 3G->2G HO (27)
1611_O2_Slough_M11-A SCOM_CM_TRIGGER_CA USE ()
8 8 8 8
A bov e 3 (0) >= 2 to < 3 (33) >= 1 to < 2 (0) Below 1 (0)

Call drops with SC 75 107 and 305 in AS. Problem seem to be missing ADJS between SC 107 and SC 77. The HO does not happen until SC 75 comes into the AS and at that point the quality is already very low. ASU putting SC 75 into the AS happens at EcN0 of -20!! In short check ADJS plan in the area (see next two slides for more details of the ADJS plan as of 30/11)
Wednesday Nov 30th

32
392
440 88 90 304 306 305 89 346 345 240 467 187 109 107 108 344
328 330 329
77 75 76
8 291 293 292 9 10
160 162 161
117
115
116 400 42 40 154 152 153 24 29 28 370 368 176 178 177 41 402 401
Wednesday Nov 30th

392
440 304 306 305 344 346345 240 467 187 144
109 107 29 108
77 75 76 291 293 292 0 161 117 115 116 400 42 40 154 152 153 24 29 28 370 368 369 389 387 388 202 200 201 176 178 41 402 401
8 9 10 139 141 140 64 66 65
177
352 354 353
59 61 6
5 99 101
Wednesday Nov 30th

100
322 323
362 360

Call drops with SC 24, 210 and 405 in the AS The is one of the drops/failures that happens every week on M4 Checking adjacencies shows that most are already in the list but perhaps SC 297 should be part of the ADJS list of SC 24 (see ADJS as of 30/11 on next slide)
Wednesday Nov 30th

SC 24 Lower set SC 210 Middle set SC 405 upper set
310 148 147
282281
194 192 264 416 482 480 481 193 299 301 300
184

162 160 161
328 330 329
208 408 209 210 315 317 316 296 298 297 75 77 76 104 106 105 130 128 129
496 498 497
26 24 25 98 97 96 67 65 40 42 41 66 112 114 113 405 16 18 17 42 40 41
40
232 354 352 234 233 384 386 385
362 360 361
353
256 320 81
Wednesday Nov 30th

322 321
83 82 408
218 2 217
203
Missing ADJ Ex 6: MTC dropped call (09:08:12:400)

Call is started on SC 306. Then SC 305 is added and a little later 306 is removed as UE passes the site (10181) SC 305 becomes very bad (on figure on the right, the upper line is 306 while the lower line is for SC 305) Missing ADJS to 344 and 346 (see next page)
Friday Dec 16th

Missing ADJ Ex 6: MTC dropped call (09:08:12:400)
248
409 216 32 392
440 61 59 60 88 90 89 304 306 305 344 346 345
ADJS (blue) of SC 305 (Red)
48 50 49
187 168 170 169 328 330329 109 107 108
146 144 145
77 75 76 291 293 292 160 162 161 117 115
224 25
116 400
339 341 340 154 152 153
42 40 41
402
401
Friday Dec
103 2005 Nokia
16th
24 29 56 1
UE sends several MR e1a but to late because SC 192 is already bad. Most likely caused by a missing ADJS between SC 250 and SC 192 (see next slide)
104 2005 Nokia
Monday Feb 27th


67, (304), (11520), (011851) 67, (314), (31392), (004594) 67, (328), 67, (312), (11392), (004594) 67, (313), (21392), (004594) 67, (336), (11443), (018599) 67, (330), (31 67, (32
67, (128), (11306), (003404) 67, (129), (21306), (003404) 67, (130), (31306), (003404) 67, (57), (21299), (000886) 67, (58), (31299), (000886) 67, (200), (11324), (033452) 67, (202), (31324), (033452) 67, (201), (21324), (033452) 67, (31310), (004873) 67, (138),(136), (11310), (004873) 67, (137), (21310), (004873) 67, (168), (11305), (003184) 67, (333), (31898), (000395) 67, (21898), (000395) 67, (332),(331), (11898), (000395) 67, (91), (11389), (002194) 67, (93), (31389), (002194) 67, (92), (21389), (002194) 67, (192), (11298), (000014) 67, (194), (31298), (000014) 67, (193), (21298), (000014) 67, (352), (11194), (01207 67, (354), (31194), (012075) 67, (353), (21194), (012075 67, (48), (11311), (004875) 67, (50), (31311), (004875) 67, (49), (21311), (004875) 67, (250), (31447), (005460) 67, (248), (11447), (005460) 67, (249), (21447), (005460) 67, (170), (31305), (003184) 67, (169), (21305), (003184) 67, (240), (11395), (004874) 67, (242),(241), (21395), (004874) 67, (31395), (004874) 67, (56), (11299), (000886) 67, (160), (11402), (00 67, (162), (31402), (005479) 67, (161), (21402), (005
67
67, (176), (11302), (001472) 67, (177), (21302), (001472) 67, (178), (31302), (001472)
67, (81), 67, (120), (11309), (004497) 67, (83), (3 67, (8 67, (122), (31309), (004497) 67, (121), (21309), (004497) 67, (170), (11525), (001565)
Monday Feb 27th

105 2005 Nokia
67, (171), (21525), (001565) , (172), (31525), (001565)
67, (216), (11300), (000888) 67, (267), (13400), (003052) 67, (269), (33400), (003052) 67, (268), (23400), (003052) 67, (217), (21300), (000888) 67, (218), (31300), (000888) 66, 66, (22 66
Typical failures
Missing message (e.g. no L3 messages for several minutes) Cell reserved (Not seen for a while but it is an easy check in Actix) Collision between LAC update/Registration and Call attempt Call failures because of user busy (MOC) Calls disconnected by measurements system Calls disconnected by the network Missing radio bearer setup message
Investigation ongoing showing loss of radio link synchronisation
Missing adjacencies leading to a call failure or a dropped call Poor coverage/quality


Poor coverage/quality
Actual poor coverage is mainly seen on the border of the 3G coverage area. The grouping of the problems is not necessarily precise but it is similar to the split-up shown in the table below. Following slides shows some examples of poor coverage/quality Note that often a missing adjacency can look like poor coverage but is poor quality.
RSCP Good EcN0 Good Poor No problem Interference/quality Poor Possible problem Interference/Coverage
Poor coverage/quality ex 1: MTC Dropped call (13:35:29:360)

SC 130 is only cell in AS. Within 1 sec SC 130 drops from EcN0 of -7 to -13 and a second later it is at -23. SC 104 is at the same time in monitored set starting from about -13 but ending at -7 when the call drops Conclusion: The drop is caused by a sudden drop in quality. Possibly by going around the corner
O2_Bham_0711-Uu_Tec hnology _Mode (N/A ) UMTS Mode (122410) GSM mode (36097) O2_Bham_0711-CPICH_A llSets _UE_Ec No_For_SC_130 (dB)
( ( ( ( ( ( (
Monday Nov 7th

Poor coverage/quality ex 2: MOC Failed Call (12:18:32:970)

Call initiated on SC 186 (Cell Id 31007 RNCId 61). SC 185 is then added to AS After RAB setup Complete the UE sends several e1a reports for SC 56 and SC 233 but the EcN0 of the active set is already at about -15 and drops to -24dB within 1-2 seconds. Seems to be interference/site problems based on the fact of very low EcN0 at a RSCP level of -89 to -92dB (see next slide for more details)
Wednesday Nov 16th

Poor coverage/quality ex 2: MOC Failed Call (12:18:32:970)

AS and MR information
Wednesday Nov 16th

SC
EcN0 RSCP
Poor coverage/quality ex 3: MOC Dropped Call (09:08:09:790)
UE is in a known poor coverage area. UE is hanging on to a 3G cell about 7.5 km away (see next slide for available cell and ADJS). There have been several attempts to find a 2G cell but they are unsuccessful. Check ADJGs and/or reduce the coverage of the site
Friday Mar 3rd

Poor coverage/quality ex 3: MOC Dropped Call (09:08:09:790)

Drop Call here
Call active on this site
Friday Mar 3rd

Slide with signal from Actix for previous page
Typical failures


Overshooting cell example: MTC Failed Call (13:53:51:530)

UE starts the call on SC 440 (cellid 11907, RNC 63) which is far away (about 11km). UE reports 293 which is in the local area but actually RNC believes it to be the ADJS of cell 11907
Wednesday Mar 1st

Overshooting cell example: MTC Failed Call (13:53:51:530)
Trying to connect to this cell
Mobile is here
Wednesday Mar 1st

Typical failures


OTHER
MOC Dropped Call (17:02:37:460)
Call is disconnected by the user/UE. NW sends CC Alerting and CC Connect for ps_Domain and UE responds with RRCStatus protocolErrorInformation
Monday Feb 27th

Signalling with ProtocolError Information
MTC Dropped Call (15:44:05:520)

Call is started at SC 26 (CellId 31312, RNC 67). ASU to (26,210) -> (210) -> (210,26) -> (210,77,26) -> (297,210,26) -> (297,77,210) -> (297) Rapid drop in EcN0, e1f for SC 297 but EcNo at -19 to -21 and the call drops while doing the 2G measurements
O2_Slough_M11_0811-Uu_Tec hnology _Mode (N/A ) UMTS Mode (194297) GSM mode (37555) O2_Slough_M11_0811-CPICH_A llSets _UE_Ec No_For_SC_297 (dB)
Tuesday Nov
120 2005 Nokia
8th
( ( ( ( ( ( (
MOC failed Call (09:53:33:600)

Call fails on SC 234 (Cell Id 31690) MR e1a for SC 232 is sent first time at EcN0 of -8 for SC 234. Several e1a for SC232 is send but no ASU is received and in the end the call fails due failing softer handover
2111_O2_Slough_M11-Uu_Tec hnology _Mode (N/A ) UMTS Mode (195327) GSM mode (45793) 2111_O2_Slough_M11-CPICH_A llSets _UE_Ec No_For_SC_234 (dB)
Monday Nov 21st

( ( ( ( ( ( (
MTC Dropped Call (19:35:38:830)
UE has 202 as the only cell in AS. As 202 becomes bad UE sends MR e1a for SC 73, 208 and 333 but no ASU is received from the network. After drop UE reselects to SC 208 Investigation of counters etc for cell with SC 202 (CI 31324)
Monday Feb 27th

MTC Failed Call (16:05:01:430)

Two RRC connection request send on RNC 61, CI 11134 at EcIo of -11 to -12 but there are no reply from the network. Need to check cell for performance
Thursday Mar 23rd


Coaching Session - 3G Voice Call Analysis - v04

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Coaching Session - 3G Voice Call Analysis - v04

Enviado por

Direitos autorais:

Formatos disponíveis

3G Voice Call Analysis

Analysis of drive test log files

NOT discussing Counters, Logging equipment, analysing tools, RNC logging.

Overview of Radio Resource Management Signalling in a normal successful call

NAS Messages Core

SWPRB Internal Messages RANAP Messages

CS Radio Interface Protocol (RIP) User Plane

MAC FP AAL2 ATM Phy

Link Layer Phy

Link Layer Phy Phy

CS Radio Interface Protocol (RIP) Control Plane

MAC FP AAL2 ATM Phy

Iub Protocol Stack

Iu-cs Protocol Stack

Radio Network Control Plane RANAP

Transport Network Control Plane

User Plane Iu User Plane Protocol

Radio Resource Management (RRM): Tasks

RT services must have higher quality assurance than NRT

Radio Resource Management (RRM): Functions

Radio Resource Management (RRM): Conn. based functions

Handover Control (HC)

Radio Resource Management (RRM): Cell based functions

Load Control (LC)

Admission Control (AC)

Resource Management (RM)

Signalling for a Successful AMR Call

Mobile Terminated Call (MTC) - I

RRC CONNECTION SETUP (FACH)

Mobile Terminated Call (MTC) - II

SCCP: CONNECTION REQUEST SCCP: CONNECTION CONFIRM

Mobile Terminated Call (MTC) - III

RADIO BEARER SET-UP (DCCH) RADIO BEARER SET-UP COMPLETE (DCCH)

RANAP RANAP RANAP RANAP

MTC Call Established

Mobile Originated Call (MOC) - I

RRC CONNECTION SETUP (FACH)

SCCP: CONNECTION REQUEST

Mobile Originated Call (MOC) - II

Mobile Originated Call (MOC) - III

RADIO BEARER SET-UP (DCCH) RADIO BEARER SET-UP COMPLETE (DCCH)

RANAP RANAP RANAP RANAP

MOC Call Established

Timer T312 started

UE receives RRC Connection Setup message

UE receives in sync indicators on L1

N312 L1 in sync indicators

Admission Control Summary

Load change information

Load Control Producing of load information

P rx_nc + P rx_nc P rx_target

If the resulting power is still below PtxTraget the RAB is admitted

Admission Control in RRC Request

Admission Control in RAB Assignment

Admission Control Functional overview

Mobile Originated Release

RANAP RANAP RANAP RANAP RANAP

The Call and all resources are released

Mobile Terminated Release

RANAP RANAP RANAP RANAP RANAP

The Call and all resources are released

Active Set Update