Vous êtes sur la page 1sur 108

Nokia Networks

Nokia Academy
Call Drop and Mobility Optimization
RN3705 – 50A

RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Copyright and confidentiality

The contents of this document are proprietary and Feedback may be used in Nokia Solutions and Networks limited to, the implied warranties of merchantability and
confidential property of Nokia Solutions and Networks. products and related specifications or other fitness for a particular purpose, are made in relation to
This document is provided subject to confidentiality documentation. Accordingly, if the user of this the accuracy, reliability or contents of this document.
obligations of the applicable agreement(s). document gives Nokia Solutions and Networks feedback NOKIA SOLUTIONS AND NETWORKS SHALL NOT BE
on the contents of this document, Nokia Solutions and RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS
This document is intended for use of Nokia Solutions Networks may freely use, disclose, reproduce, license, DOCUMENT or for any loss of data or income or any
and Networks customers and collaborators only for the distribute and otherwise commercialize the feedback in special, incidental, consequential, indirect or direct
purpose for which this document is submitted by Nokia any Nokia Solutions and Networks product, technology, damages howsoever caused, that might arise from the
Solutions and Networks. No part of this document may service, specification or other documentation. use of this document or any contents of this document.
be reproduced or made available to the public or to any
third party in any form or means without the prior Nokia Solutions and Networks operates a policy of This document and the product(s) it describes are
written permission of Nokia Solutions and Networks. ongoing development. Nokia Solutions and Networks protected by copyright according to the applicable laws.
This document is to be used by properly trained reserves the right to make changes and improvements
professional personnel. Any use of the contents in this to any of the products and/or services described in this Nokia is a registered trademark of Nokia Corporation.
document is limited strictly to the use(s) specifically document or withdraw this document at any time Other product and company names mentioned herein
created in the applicable agreement(s) under which the without prior notice. may be trademarks or trade names of their
document is submitted. The user of this document may respective owners.
voluntarily provide suggestions, comments or other The contents of this document are provided "as is".
feedback to Nokia Solutions and Networks in respect of Except as required by applicable law, no warranties of © Nokia Solutions and Networks 2015
the contents of this document ("Feedback"). Such any kind, either express or implied, including, but not

2 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Module Objectives

At the end of the module you will be able to:

• monitor and analyze key aspects of call retainability using


network observability
• examine sample or live measurement data for call drop and
mobility issues
• propose optimisation actions to resolve call drop issues

4 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Content
Introduction
-Terms definition
-Phases of RRC connection and RAB
-Call drop analysis Overview

Call/Session Drop monitoring & analysis


- RRC/RAB/SHO active
- HSPA active/SCC

5 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Content
Introduction
-Terms definition
-Phases of RRC connection and RAB
-Call drop analysis Overview

Call/Session Drop monitoring & analysis


- RRC/RAB/SHO active
- HSPA active/SCC

6 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Introduction
RRC and RAB phases

RRC connection setup Phase: Setup Access Active


RAN resources are reserved for signaling connection
between UE and RNC
RRC access Active
Connection between UE and RRC Setup Access Complete

Success
RRC active Complete Complete
UE has RRC connection. If dropped, also active RAB is Active

Access
dropped. Release
RAB setup
Attempts to start the call Active
Attempts

RAB setup access


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

7 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Content
Introduction
-Terms definition
-Phases of RRC connection and RAB
-Call drop analysis Overview

Call/Session Drop monitoring & analysis


- RRC/RAB/SHO active
- HSPA active/SCC

8 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Introduction
BTS RNC
RRC Connection Setup & Access and Active UE CN

RRC: RRC connection Request

RRC SETUP phase


RRC SETUP fails if some of the needed resources (RNC, BTS, AIR,

RRC Setup time


(Resource Reservation in RNC, BTS, Transport)
Transport) are not available. When an RRC setup failure occurs the RNC
RRC: RRC connection Setup
sends an RRC: RRC CONNECTION REJECT message to UE
RRC ACCESS phase
(RNC waits for Reply from UE)
RRC: RRC connection Setup Complete
RRC ACCESS fails if the UE does not reply to RRC: RRC CONNECTION
SETUP message with the RRC: RRC CONNECTION SETUP COMPLETE RRC ACTIVE phase
message in given time, if the BTS reports a radio link synchronization RRC: Initial Direct Transfer
failure or in an RNC internal failure occurs
RANAP: Initial UE Message

UE-CN Signaling
RRC ACTIVE fails when an interface related (Iu, Iur , Iub, or Radio) or RNC (E.g. RAB Establishment and Release)

internal failure occurs, and the failure causes the release of the RRC
RANAP: Iu Release Command
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 RRC: RRC connection Release
COMMAND message (s) 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
9 RN3705EN50GLA0 © Nokia Solutions and Networks 2015
This page contains no comments
Introduction
RAB Setup & Access and Active UE BTS RNC CN

RRC Connection Active Phase, UE-CN Signaling

RAB SETUP fails if some of the needed resources (RNC, BTS, AIR, Transport) are not RANAP: RAB Assignment Request

available. When an RAB setup failure occurs the RNC sends a RANAP: RAB ASSINGMENT RAB SETUP phase

RAB Setup time


RESPONSE message to the CN with an appropriate failure cause (Resource Reservation in RNC, BTS, Transport)

RRC: Radio Bearer Setup


RAB ACCESS phase

RAB ACCESS fails if the UE replies with an RRC: RADIO BEARER SETUP FAILURE message
(RNC waits for Reply from UE)

or the connection cannot be established in a give time. When a RAB access failure occurs, RRC: RB Setup Complete
RANAP: RAB Assignment Response
the RNC sends a RANAP: RAB ASSINGMENT RESPONSE message to the CN with an
RAB ACTIVE phase
appropriate failure cause. Immediately after this, the RNC sends also a RANAP: IU
(User Plane Data Transfer)
RELEASE REQUEST to the CN and waits for RANAP: IU RELEASE COMMAND message
RANAP: RAB Assignment Request with IE: RAB reconfiguration
RAB Holding Time

RAB Reconfiguration Actions

RAB ACTIVE fails when an interface related (Iu, Iur, Iub, or Radio) or RNC internal failure
(Reconfigure RAB resources in RNC, BTS, Transport)
RRC: RB Reconfiguration
occurs, and the failure causes the release of the RAB connection. RRC: RB Reconfiguration Complete
• If the UE has more than one RAB connection and the failure is not so critical that it RANAP: RAB Assignment Response
would lease to an RRC Connection drop, only the failed RAB connection is released. The RANAP: RAB Assignment Request with IE: RAB Release
RNC sends a RANAP: RAB RELEASE REQUEST message to the CN and waits for a RANAP: RRC: Radio Bearer Release
RAB RELEASE COMMAND or RANAP: IU RELASE COMMAND from CN RRC: Radio Bearer Release Complete
• Otherwise, both the RRC connection and RAB connection (s) are released. The RNC RANAP: RAB Assignment Response
send a RANAP: IU RELASE REQUEST message to the CN and waits for a RANAP: IU Release RAB resources in RNC, BTS,
RELEASE COMMAND MESSAGE from the CN Transmission

10 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Content
Introduction
-Terms definition
-Phases of RRC connection and RAB
-Call drop analysis Overview

Call/Session Drop monitoring & analysis


- RRC/RAB/SHO active
- HSPA active/SCC

11 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Introduction
Call drop analysis Overview Top (N) drops
Neighbors’ Performance Traffic
(use SHO success per adjs
counters to identify badly
Cell and its Neighbor
performing neighbors) & Map
Cells availability Site OK ?
Alarms/Tickets Audit adjacent sites for
alarms, Availability,
YES configuration and capacity
NO
Configuration &
Parameter audit Conf OK ?
3G Cell at RNC YES Iur
border? performance Investigation Iur
YES

SHO SHO Success YES


Rate < 90%?

NO New site ?

ISHO NO Analyse last detailed RF and IFHO neighbor


ISHO
Failures radio measurements optimisation

YES
3G cell covers
3G cell at inter-
over a
RNC border ?
Top coverage hole?
issues
No cell found YES RF and ISHO neighbor
ratio >40 % optimisation
2G Cell Doctor
NO

No cell found
2G Investigation : TCH ISHO Wrong reference clock
YES ratio > 90 % and
blocking or TCH seizure Success Rate (10MHz tuning)
enough ADJG
failure (interference) < 90%

12 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Introduction
Call Drop Analysis
1. Check high call drop cells and its neighboring cells of any faulty alarms
2. Identify call drop root cause failure distribution and main failure contributor (radio, Iu, BTS, Iur,
MS, RNC)
3. Check SHO KPI if performance < 90% ( leads to radio failure)
• Check if cells are at RNC border (check Iur capacity and SRNC relocation problem)
• Detect badly performing neighbors using HO success rate per adjacency counters (M1013)
• High incoming HO failure rate in all ADJS – check sync alarms
• Assessing neighbor list plan and visualization check with map
• Evaluate HO control parameters and trigger threshold
4. Check ISHO KPI if RT ISHO < 90% or NRT < 80% (leads to radio failure)
• Check missing neighbor (M1015), GSM frequency plan neighbor RNC and MSC database consistency
audit, check alarm of reference clock in 3G or in 2G, check 2G TCH congestion
• Check RRC Drop ISHO RT / NRT

13 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Introduction
Call Drop Analysis
5. Detecting DL or UL path loss problem if RAB drop due to radio (dominant call drop cause > 50%)
• Check ASU failure rate (UNSUC_ASU) which link to NO RESPONSE FROM RLC
• Mapping radio failures with Tx power and CPICH related parameters -> CPICHToRefRABOffset, PTXDPCH
MAX
• Check Call reestablishment timer -> T315 (rec.10s)
• Ecno distribution for bad coverage issue (M1007C38-M1007C47)
6. Check core network parameter setting if RAB_ACT_FAIL_XXX_IU
• Check SCCP SGSN/RNC IuPS Tias/Tiar if RAB_ACT_FAIL_PS_BACKG_IU
7. If high RAB_ACT_FAIL_XXX_BTS
• Check if any BTS faulty alarm (7653 cell faulty alarm)
• If no alarms, COCO detach/attach
8. If high RAB_ACT_FAIL_XXX_MS
• Check physical channel reconfiguration failure rate (IFHO, ISHO, code optimisation)

14 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Content
Introduction
-Terms definition
-Phases of RRC connection and RAB
-Call drop analysis Overview

Call/Session Drop monitoring & analysis


- RRC/RAB/SHO active
- HSPA active/SCC

15 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Content
Introduction
-Terms definition
-Phases of RRC connection and RAB
-Call drop analysis Overview

Call/Session Drop monitoring & analysis


- RRC/RAB/SHO active
- HSPA active/SCC

16 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
RAB & RRC Active Failures
• RAB and RRC active failure reasons:
- RNC Internal
- BTS
UE RNC CORE
- UE
RAB Assignment Request (setup)
- Radio Interface
- Iur Radio Bearer Setup
- Iu
Radio Bearer Setup Complete
- Ciphering
- Integrity check RAB Assignment Response

• RAB and RRC normal release:


- RAB active complete New Counters for HHO, ISHO and RAB Assignment Request (release)
- Pre-emption GANHO added in RU20, earlier
Iu Release Command

- SRNC Relocation included to RAB_act_rel_SRNC


RAB Assignment Response
- HHO, ISHO, GANHO Iu Release Request

- Unspecific error in CN

17 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
Example: RRC Active failures

Major cause Radio

18 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
Example: RAB active failures - Voice

Major cause Radio

19 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
Example: RAB active failures - PS

Major cause Radio

20 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
Transport failures separation in RRC/RAB Active
• transport failure counters
• M1001C689, RRC ACTIVE FAIL DUE TO TRANS
• M1001C690, RAB ACTIVE FAILURES DUE TO TRANS FOR CS VOICE
• M1001C691, RAB ACTIVE FAILURES DUE TO TRANS FOR CS DATA CONV
• M1001C692, RAB ACTIVE FAILURES DUE TO TRANS FOR CS DATA STREAM
• M1001C693, RAB ACTIVE FAILURES DUE TO TRANS FOR PS DATA STREAM
• M1001C694, RAB ACTIVE FAILURES DUE TO TRANS FOR PS DATA INTERA
• M1001C695, RAB ACTIVE FAILURES DUE TO TRANS FOR PS DATA BACKG

When the RNC initiates RAB release either using RANAP: IU RELEASE REQUEST or RANAP:
RAB RELEASE REQUEST after a transmission failure happened.

21 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
SHO Overhead

•SHO OH
 Total _ Number _ of _ Radio _ Links 
SHO _ Overhead = 100% ×  − 1
 Number _ of _ Best _ Server _ Radio _ Links 

•Check SHO Overhead (RNC_192b) to see how big is SHO area, if it is too small SHO may fails and if too big
capacity is wasted
100 * ( sum((ONE _ CELL _ IN _ ACT _ SET _ FOR _ RT + ONE _ CELL _ IN _ ACT _ SET _ FOR _ NRT ) *1
+ (TWO _ CELLS _ IN _ ACT _ SET _ FOR _ RT + TWO _ CELL _ IN _ ACT _ SET _ FOR _ NRT ) * 2
+ (THREE _ CELLS _ IN _ ACT _ SET _ FOR _ RT + THREE _ CELL _ IN _ ACT _ SET _ FOR _ NRT ) * 3)
SHO _ Overhead = −1
sum(ONE _ CELL _ IN _ ACT _ SET _ FOR _ RT + ONE _ CELL _ IN _ ACT _ SET _ FOR _ NRT
+ TWO _ CELLS _ IN _ ACT _ SET _ FOR _ RT + TWO _ CELL _ IN _ ACT _ SET _ FOR _ NRT
+ THREE _ CELLS _ IN _ ACT _ SET _ FOR _ RT + THREE _ CELL _ IN _ ACT _ SET _ FOR _ NRT )

•SHO success (RNC_195a)


100 * sum( SUCC _ UPDATES _ ON _ SHO _ FOR _ RT + SUCC _ UPDATES _ ON _ SHO _ FOR _ NRT )
SHO _ Success _ ratio =
sum(CELL _ ADD _ REQ _ ON _ SHO _ FOR _ RT + CELL _ REPL _ REQ _ ON _ SHO _ FOR _ RT
+ CELL _ DEL _ REQ _ ON _ SHO _ FOR _ RT + CELL _ ADD _ REQ _ ON _ SHO _ FOR _ NRT
+ CELL _ REPL _ REQ _ ON _ SHO _ FOR _ NRT + CELL _ DEL _ REQ _ ON _ SHO _ FOR _ NRT )

22 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
SHO Success per Adjacency

• Detect badly performing neighbors using SHO success rate per adjacency counters (M1013)
• There is also similar kind of counters for IFHO and ISHO

• SHO Success per Adjacency (M1013 AutoDef SHO)


100 * sum( SHO _ ADJ _ INTRA _ FREQ _ SHO _ COMPL)
SHO _ success _ per _ ADJS =
sum( SHO _ ADJ _ INTRA _ FREQ _ SHO _ ATT )

• IFHO Success per Adjacency (M1014 AutoDef IFHO)


100 * sum( HHO _ ADJ _ INTER _ FREQ _ HHO _ COMPL)
IFHO _ success _ per _ ADJI =
sum( HHO _ ADJ _ INTER _ FREQ _ HHO _ ATT )

• ISHO Success per Adjacency (M1015 AutoDef ISHO)


100 * sum( HO _ ADJ _ INTER _ SYS _ HHO _ COMPL)
ISHO _ success _ per _ ADJG =
sum( HO _ ADJ _ INTER _ SYS _ HHO _ ATT )

23 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
Active Set Update Failure Counters

•Using counters below it is possible to monitor Active Setup Update failures


Counter Name Counter ID Update Cause
When an RRC: ACTIVE SET UPDATE message is sent by the serving RNC to the UE for adding one or more radio links to the
active set. The counter is updated by the number of radio links that are attempted to be added to the active set, also in a cell
AS_UPDATE_RL_ADD_ATT M1006C121
replacement procedure. The counter is updated for the cells that are attempted to be added to the active set. In case of a DRNC
cell, the WBTS-0/WCEL-0 object is used

When the serving RNC receives an RRC: ACTIVE SET UPDATE COMPLETE message from the UE, this counter is updated by the
AS_UPDATE_RL_ADD_SUCC M1006C122 number of radio links added with the active set update procedure, also in a cell replacement procedure. The counter is updated
for the cells which were added to the active set. In case of a DRNC cell, the WBTS-0/WCEL-0 object is used

When the serving RNC receives an RRC: ACTIVE SET UPDATE FAILURE message from the UE, this counter is updated by the
number of radio links that were attempted to be added to the UE's active set with the active set update procedure, also in a cell
AS_UPDATE_RL_ADD_FAIL_UE M1006C123
replacement procedure. The counter is updated for the cells which were attempted to be added to the active set. In case of a
DRNC cell, the WBTS-0/WCEL-0 object is used.

When the serving RNC does not receive a reply to an RRC: ACTIVE SET UPDATE message sent to the UE, this counter is
updated by the number of radio links that were attempted to be added into the UE's active set with the active set update
AS_UPDATE_RL_ADD_NOREPLY M1006C124
procedure, also in a cell replacement procedure. The counter is updated for the cells which were attempted to be added into the
active set. In case of a DRNC cell, the WBTS-0/WCEL-0 object is used.

When an RRC: ACTIVE SET UPDATE message is sent by the serving RNC to the UE for deleting one or more radio links to the active
set. The counter is updated by the number of radio links that are attempted to be deleted from the active set, also in a cell replacement
AS_UPDATE_RL_DEL_ATT M1006C125
procedure. The counter is updated for the cells that are attempted to be deleted from the active set. In case of a DRNC cell, the WBTS-
0/WCEL-0 object is used.

When the serving RNC receives an RRC: ACTIVE SET UPDATE COMPLETE message from the UE, this counter is updated by the
AS_UPDATE_RL_DEL_SUCC M1006C126 number of radio links deleted from the active set update procedure, also in a cell replacement procedure. The counter is
updated for the cells which were deleted from the active set. In case of a DRNC cell, the WBTS-0/WCEL-0 object is used

24 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
Active Set Add/Del success- example, RNC

0.9999 0.04%

0.9998
0.04%
Some failures due
to no reply to ASU
0.9997
0.03%
0.9996

0.03%
0.9995
AS_UPDATE_RL_ADD_SUCC %
AS_UPDATE_RL_DEL_SUCC %
0.9994 0.02%
AS_UPDATE_RL_ADD_FAIL_UE %
AS_UPDATE_RL_ADD_NOREPLY %
0.9993
0.02%

0.9992
0.01%
0.9991

0.01%
0.999

0.9989 0.00%
6. 08

7. 08

8. 08

9. 08

.3 8

.3 8

.3 8

.3 8

.3 8

.3 8

.3 8

.3 8

.3 8

.3 8

.3 8

.3 8

.3 8

.3 8

.3 8

.3 8

8
10 00

11 00

12 00

13 00

14 00

15 00

16 00

17 00

18 00

19 00

20 00

21 00

22 00

23 00

24 00

25 00

00
20

20

20

20

.2

.2

.2

.2

.2

.2

.2

.2

.2

.2

.2

.2

.2

.2

.2

.2
3.

3.

3.

3.

3.
5.

25 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
Example: Active Set Add FAIL_UE/NO REPPLY- (Wcel level)
25000 30

25
20000

20

15000
AS_UPDATE_RL_ADD_ATT
AS_UPDATE_RL_DEL_ATT
15
AS_UPDATE_RL_ADD_FAIL_UE
AS_UPDATE_RL_ADD_NOREPLY
10000

10

5000
5

0 0
1 18 35 52 69 86 103 120 137 154 171 188 205 222 239 256 273 290 307 324 341 358 375 392 409

26 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
SHO branch Setup failures

•SHO branch setup fail due to BTS / iub

- M1007C71 SETUP_FAIL_SHO_BRANCH_BTS :
• The number of soft handover branch setup failures due to BTS. This counter is updated for the cell(s)
where the failure occurred.
• When the SHO branch setup fails due to BTS. The BTS resources here mean either NBAP: RADIO LINK
SETUP FAILURE, NBAP: RADIO LINK ADDITION FAILURE or that RNC does not receive any answer from the
BTS.
- M1007C72 SETUP_FAIL_SHO_BRANCH_IUB :
• The number of soft handover branch setup failures due to Iub transmission. This counter is updated for
the cell(s) where the failure occurred.
• When the SHO branch setup fails due to Iub transport. The transport failures include both CAC
(Connection Admission Control) negative acknowledgements and signaling failures.

27 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
Example: SHO branch Setup failures distribution

BTS Failures dominant

28 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
Packet Call Analysis

Packet call normal releases (normal end of the call) counters includes
• Transition to DCH 0/0, Cell_FACH or Cell_PCH due to inactivity or low utilization
• Outgoing SRNC relocation
• Inter-RNC hard handover Release due to RL Failure counters:

• Inter-system Hard Handover M1022C57 PS_REL_RL_FAIL_HS_E_INT


M1022C58 PS_REL_RL_FAIL_HS_E_BGR
Packet call Failures are divided into M1022C59 PS_REL_RL_FAIL_HS_D_INT

• RL fail M1022C60 PS_REL_RL_FAIL_HS_D_BGR


M1022C61 PS_REL_RL_FAIL_D_D_INT
• Other M1022C62 PS_REL_RL_FAIL_D_D_BGR

• Pre-emption are incremented in case RL Failure is received from BTS and cannot be acquired back during
specific time

Release due to Other Failure counters:


Release due to Pre-Emption counters:
M1022C63 PS_REL_OTH_FAIL_HS_E_INT
M1022C51 PS_REL_PRE_EMP_HS_E_INT
M1022C64 PS_REL_OTH_FAIL_HS_E_BGR
M1022C52 PS_REL_PRE_EMP_HS_E_BGR
M1022C65 PS_REL_OTH_FAIL_HS_D_INT
M1022C53 PS_REL_PRE_EMP_HS_D_INT
M1022C66 PS_REL_OTH_FAIL_HS_D_BGR
M1022C54 PS_REL_PRE_EMP_HS_D_BGR
M1022C67 PS_REL_OTH_FAIL_D_D_INT
M1022C55 PS_REL_PRE_EMP_D_D_INT
M1022C68 PS_REL_OTH_FAIL_D_D_BGR
M1022C56 PS_REL_PRE_EMP_D_D_BGR
are incremented in case the PS allocation is released due to any other reason expect normal,
are incremented in case higher priority call pre-empts the existing connection i.e. RT over NRT
pre-emption or RL failure

29 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
Packet Call Failure KPIs

Packet Call Release due the RL failures


• RNC_1095a NRT HS-DSCH/E-DCH Packet Call Release due to RL Failures
100*Sum(PS_REL_RL_FAIL_HS_E_INT + PS_REL_RL_FAIL_HS_E_BGR)
RNC_1095 a[%] =
RNC_1092 a_Packet session releases

• RNC_1096a NRT HS-DSCH/DCH Packet Call Releases due to RL Failures


• RNC_1097a NRT DCH/DCH Packet Call Releases due to RL Failures

Packet Call Release due the Other


• RNC_1098a NRT HS-DSCH/E-DCH Packet Call Releases due to Other Failures
100*Sum(PS_REL_OTH_FAIL_HS_E_INT + PS_REL_OTH_FAIL_HS_E_BGR)
RNC_1099 a[%] =
RNC_1092 a_Packet session releases

• RNC_1099a NRT HS-DSCH/DCH Packet Call Releases due to Other Failures


• RNC_1100d NRT DCH/DCH Packet Call Releases due to Other Failures

30 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
Example: Packet Call Active Failures - DCH

31 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Content
Introduction
-Terms definition
-Phases of RRC connection and RAB
-Call drop analysis Overview

Call/Session Drop monitoring & analysis


- RRC/RAB/SHO active
- HSPA active/SCC
• HSDPA Retainability
• serving cell change analysis

32 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Content
Introduction
-Terms definition
-Phases of RRC connection and RAB
-Call drop analysis Overview

Call/Session Drop monitoring & analysis


- RRC/RAB/SHO active
- HSPA active/SCC
• HSXPA Retainability
• serving cell change analysis

33 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
HSDPA Retainability Analysis

•HSDPA Retainability Failure Cause Analysis can be done based on Traffic measurements (RNC_609a) and
Packet Call measurements (RNC_920b)
•Radio link failures should be analyzed.

RNC_920b/609a< No
No Action Needed
X%

Yes

HSPA packet call Radiolink Yes


Check SCC Failure Rate – Radio, Iub, CE resource congestion
failures
No

Check CQI distribution and Ecno distribution for coverage issue

Check HSDPA mobility parameter – Add/Drop window, SCC parameter

HSPA packet call failures - Yes


Check for RNC failures and use RNC logging if required
other

34 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
HSDPA Retainability Analysis

•HSDPA Retainability Failure Cause Analysis can be done based on Traffic measurements (RNC_609a) and
Packet Call measurements (RNC_920b) - optional measurement. Radio link failures should be analyzed.

M1002C407 REL_ALLO_NORM_HS_DSCH_INT + M1002C410 REL_ALLO_NORM_HS_DSCH_BGR


RNC _ 609a = ⋅ 100%
M1002C407 REL_ALLO_NORM_HS_DSCH_INT + M1002C410 REL_ALLO_NORM_HS_DSCH_BGR +
+ M1002C408REL_ALLO_OTH_FAIL_HSDSCH_INT + M1002C411REL_ALLO_OTH_FAIL_HSDSCH_BGR +
+ M1002C479REL_ALLO_RL_FAIL_HS_DSCH_INT + M1002C482REL_ALLO_RL_FAIL_HS_DSCH_BGR

PS_REL_RL_FAIL_HS_E_INT + PS_REL_RL_FAIL_HS_E_BGR + PS_REL_RL_FAIL_HS_E_STRE


+ PS_REL_RL_FAIL_HS_D_INT + PS_REL_RL_FAIL_HS_D_BGR + PS_REL_RL_FAIL_HS_D_STRE

+ PS_REL_OTH_FAIL_HS_E_INT + PS_REL_OTH_FAIL_HS_E_BGR + PS_REL_OTH_FAIL_HS_E_STRE
+ PS_REL_OTH_FAIL_HS_D_INT + PS_REL_OTH_FAIL_HS_D_BGR + PS_REL_OTH_FAIL_HS_D_STRE
RNC_920b = ⋅ 100%
PS_REL_RL_FAIL_HS_E_INT + PS_REL_RL_FAIL_HS_E_BGR + PS_REL_RL_FAIL_HS_E_STRE
+ PS_REL_RL_FAIL_HS_D_INT + PS_REL_RL_FAIL_HS_D_BGR + PS_REL_RL_FAIL_HS_D_STRE
+ PS_REL_OTH_FAIL_HS_E_INT + PS_REL_OTH_FAIL_HS_E_BGR + PS_REL_OTH_FAIL_HS_E_STRE
+ PS_REL_OTH_FAIL_HS_D_INT + PS_REL_OTH_FAIL_HS_D_BGR + PS_REL_OTH_FAIL_HS_D_STRE

+ PS_REL_NORM_HS_E_INT + PS_REL_NORM_HS_E_BGR + PS_REL_NORM_HS_E_STRE
+ PS_REL_NORM_HS_D_INT + PS_REL_NORM_HS_D_BGR + PS_REL_NORM_HS_D_STRE
+ PS _ SWI _ HS _ E _ TO _ D _ D _ STRE + PS _ SWI _ HS _ E _ TO _ D _ D _ INT + PS _ SWI _ HS _ E _ TO _ D _ D _ BGR
+ PS _ SWI _ HS _ D _ TO _ D _ D _ STRE + PS _ SWI _ HS _ D _ TO _ D _ D _ INT + PS _ SWI _ HS _ D _ TO _ D _ D _ BGR

35 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
HSDPA Retainability Analysis

1. Identify root cause failure distribution and main contributor of low retainability
2. If high HSDPA Radio Link Failures (NRT) – dominant cause
• Compare to Cell Update ATT due to Radio link Failure (M1006C39) and Cell Update ATT due to RLC
Recoverable Error (M1006C40)
• Check Serving Cell Change success rate RNC_733b - high SCC failures lead to radio link failure
• Check CQI distribution (M5000C8-M5000C39) or Ecno distribution for bad coverage issue
(M1007C38-M1007C47, CPICH EcNo class 0-9)
• Check HSDPA FMCS Mobility Control Parameter (handover or SCC too late)
• Check call re-establishment T315 timer due to radio link failure
3. If high HSDPA Non- Radio Link Failures (NRT)
• UE responding with some failure message or not responding to some message but no RL failure
(timer expiry)
• Check RB reconfiguration, physical channel reconfiguration, NBAP RL reconfiguration failure rate
• Required ICSU log for further troubleshooting ?

36 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
Example: HSDPA Retainability
RNC_920b (M1022) vs. RNC_609a (M1002)

37 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
1
Call/Session Drop monitoring & analysis RL failures dominant cause
Example: HSDPA Retainability Failures – M1002 The number of HS-DSCH allocation
releases due to radio link failure, RLC
protocol reset or uplink RLC
unrecoverable error
Triggering of this counter does not
mean that the whole HSDPA user
plane would be deleted.
If there are other HSDPA capable
cells in the active set, serving cell
change can be triggered and if it is
successful, the "HSDPA packet call"
still continues and
M1022C59+M1022C57 is not
incremented.
Thus M1022 (Packet call) gives
better view on the end user
experience.

38 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


Page: 37
Number: 1 Author: Presenter Subject: Presentation Notes Date: 10/20/2015 3:15:55 PM
M1002 REL_ALLO_RL_FAIL_HS_DSCH_xxx
Triggering of this counter does not mean that the whole HSDPA user plane would be deleted. If there are other HSDPA capable
cells in the active set, serving cell change can be triggered and if it is successful, the "HSDPA packet call" still continues and
M1022C59+M1022C57 is not incremented. Thus M1022 (Packet call) gives better view on the end user experience.

RNC_1185b replaced for better version/ID control by RNC_2676a in RU30 (with change in formula)
RNC_1102b replaced for better version/ID control by RNC_2666a in RU30 (with change in formula)
1
Call/Session Drop monitoring & analysis
Example: HSDPA Retainability Failures – M1022

RL failures dominant cause


When a packet call is released due to a radio link failure,
that is, all radio links go out of the sync state during a
packet call and thus the dedicated user plane is
released

39 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


Page: 38
Number: 1 Author: Presenter Subject: Presentation Notes Date: 10/20/2015 3:15:55 PM
RNC_1099b replaced for better version/ID control:RNC_2196a
RNC_1096b replaced for better version/ID control:RNC_2208a
1
Call/Session Drop monitoring & analysis
Example: HSDPA Normal releases causes

40 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


Page: 39
Number: 1 Author: Presenter Subject: Presentation Notes Date: 10/20/2015 3:15:55 PM
rnc_1188b replaced for better version/ID control by RNC_2682a (in RU30 with change in formula)
rnc_1187b replaced for better version/ID control by RNC_2680a (in RU30 with change in formula)
rnc_1186b replaced for better version/ID control by RNC_2678a (in RU30 with change in formula)
Call/Session Drop monitoring & analysis
HSUPA Retainability Analysis

•HSUPA Retainability Failure Cause Analysis can be done based on Traffic measurements (RNC_919b) and
Packet Call measurements (RNC_921c)
• Analysis is similar than for HSDPA

No
RNC_919b/921c < X % No Action Needed

Yes

HSPA packet call Radiolink Yes


Check SCC Failure Rate – Radio, Iub, CE resource congestion
failures
No

Check CQI distribution and Ecno distribution for coverage issue

Check HSDPA mobility parameter – Add/Drop window, SCC parameter

HSPA packet call failures - Yes


Check for RNC failures and use RNC logging if required
other

41 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
HSUPA Retainability Analysis

•HSUPA Retainability Failure Cause Analysis can be done based on Traffic measurements (RNC_919b) and
Packet Call measurements (RNC_921c)

(REL_EDCH_NORM_INT + REL_EDCH_NORM_BGR + )
RNC_919b = ⋅100%
(REL_EDCH_NORM_INT + REL_EDCH_NORM_BGR
+ REL_EDCH_RL_FAIL_INT + REL_EDCH_RL_FAIL_BGR
+ REL_EDCH_OTHER_FAIL_INT + REL_EDCH_OTHER_FAIL_BGR)

sum( PS _ REL _ RL _ FAIL _ HS _ E _ STRE + PS _ REL _ RL _ FAIL _ HS _ E _ INT + PS _ REL _ RL _ FAIL _ HS _ E _ BGR
+ PS _ REL _ OTHER _ FAIL _ HS _ E _ STRE + PS _ REL _ OTHER _ FAIL _ HS _ E _ INT + PS _ REL _ OTHER _ FAIL _ HS _ E _ BGR)
RNC _ 921c = 100 − 100 *
sum( PS _ REL _ RL _ FAIL _ HS _ E _ STRE + PS _ REL _ RL _ FAIL _ HS _ E _ INT + PS _ REL _ RL _ FAIL _ D _ D _ BGR
+ PS _ REL _ OTHER _ FAIL _ HS _ E _ STRE + PS _ REL _ OTHER _ FAIL _ HS _ E _ INT + PS _ REL _ OTHER _ FAIL _ HS _ E _ BGR
+ PS _ REL _ NORM _ HS _ E _ STRE + PS _ REL _ NORM _ HS _ E _ INT + PS _ REL _ NORM _ HS _ E _ BGR
+ PS _ SWI _ HS _ E _ TO _ D _ D _ STRE + PS _ SWI _ HS _ E _ TO _ D _ D _ INT + PS _ SWI _ HS _ E _ TO _ D _ D _ BGR
+ PS _ SWI _ HS _ E _ TO _ HS _ D _ STRE + PS _ SWI _ HS _ E _ TO _ HS _ D _ INT + PS _ SWI _ HS _ E _ TO _ HS _ D _ BGR)

42 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
Example: HSUPA Retainability
RNC_921b (M1022) vs. RNC_919a (M1002)

43 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
HSUPA Retainability Analysis

• There are several reasons for HSUPA release:


• RNC_1108a E-DCH Rel due to RL Failures
• RNC_1109a E-DCH Rel due to other failures

• RL fail is incremented If:


• a radio link failure happens during HSDPA call
• uplink RLC unrecoverable error happens (Cell Update by UE)
• RLC-entity in RNC reports RLC protocol reset

44 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
HSDPA retainability & SCC success
•There seems not to be a relation with poor SCC success and HSDPA retainability, as seen in the picture below.
RNC_733a SCC success rate for HSDPA and HSUPA is not very accurate in cell level as denominator is incremented in the
source cell (old serving cell) and numerator is incremented in the target cell (new serving cell).
• RU30 System program report contains new formula RNC_733b

250.00 101.00

100.00

200.00
99.00

98.00
150.00

RNC_609a
97.00

100.00
96.00

95.00
50.00

94.00

0.00 93.00
1 3 5 7 9 11 13 15 17 19 21 23 25 27 29 31 33 35 37 39 41 43 45 47 49 51 53 55 57 59 61 63 65 67 69 71 73 75 77 79 81

RNC_733a_SCC SR RNC_918a_HSUPA_SCC SR RNC_609a_HSPDA_Retainability

45 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Content
Introduction
-Terms definition
-Phases of RRC connection and RAB
-Call drop analysis Overview

Call/Session Drop monitoring & analysis


- RRC/RAB/SHO active
- HSPA active/SCC
• HSDPA Retainability
• serving cell change analysis

46 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
HSDPA SCC Analysis

HSDPA SCC Success Rate

No No action
RNC_733b < X %
needed

Top N cells Yes


No No No No No
SCC Fail SCC Fail
SCC Fail BTS SCC Fail AC SCC Fail UE SCC Fail Others
Transmission Prevention timer

Yes Yes Yes


Yes Yes Yes

Check
Check RNC internal HSDPACellChan
Check CE DL power Check AAL2 Iub Check RB geMinInterval
transport resources
resource usage congestion resource reconfiguration parameter
(DMPG) – ICSU
at BH BH ? congestion at BH Failure rate troubleshooting

No

No
Check Maximum
code tree
number of
congestion BH
HSDPA users

47 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
Intra-BTS serving cell change

• 1. Serving cell change started due to active set update

• 2. Serving cell change started due to CPICH Ec/No

• 3. Serving cell change started due to UL SIR Error


• 4. Serving cell change started due to other reason (e.g. RL Failure, event 6F)
• 5. Serving cell change prevented due to timer
• 6. Serving cell change failure due to AC

• 7. Serving cell change failure due to BTS

• 8. Serving cell change failure due to transport


• 9. Serving cell change failure due to UE
• 10. Number of successful intra-BTS serving cell changes

• Attempt and failure counters are updated to the current serving cell.
Successful counters are updated to the new serving cell

48 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
Intra-BTS serving cell change

• 1. Serving cell change started due to ASU update


• 2. Serving cell change started due to CPICH Ec/No
• 3. Serving cell change started due to UL SIR Error
• 4. Serving cell change started due to other reason (e.g. RL Failure, event 6F)
• 5. Serving cell change prevented due to timer

• 6. Serving cell change failure due to AC


• 7. Serving cell change failure due to BTS
• 8. Serving cell change failure due to transport
• 9. Serving cell change failure due to UE

• 10. Number of successful inter-BTS serving cell changes

49 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
HSDPA SCC analysis
1. Determine SCC success rate, SCC failure rate and failure cause distribution
2. Check target cells HSDPA Setup performance (M1002C401 – M1002C428) if source cells SCC failure
rate is high
• To find out which target cells are causing the SCC failure

1. If high SCC_FAILED_due_to_AC
• Check target cells M1000C22 AVE_PTXTOT_CLASS_4 and M1000C20 AVE_PTXTOT_CLASS_3 if SCC failures due to the lack of
DL power (SCC_Failed_due_to_AC) – this is not visible in HSDPA accessibility KPI
• Check target cells number of simultaneous active HSDPA users

2. If high SCC_FAILED_due_to_BTS
• Check target cells M1002C416/424 SETUP_FAIL_BTS_HS_DSCH_XXX
• Check target cells CE resource utilization at BH using M5001 counters for lack of UL return channel resource
• Check NBAP Radio Link Reconfiguration Failure rate
• Check SHO overhead – all branches must have enough CE capacity if UE is in SHO when HS-DSCH allocation is started

3. If high SCC_FAILED_due_to_UE
• Check target cells M1002C415/423 SETUP_FAIL_UE_HS_DSCH_XXX
• Check RB reconfiguration Failure rate
• Require ICSU troubleshooting for UE types monitoring

50 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
HSDPA SCC analysis

4. If high SCC_FAILED_due_to_TRANS
• Check target cells of M1002C414 SETUP_FAIL_IUB_MAC_D_INT or M1002C422 SETUP_FAIL_IUB_MAC_D_BGR
• Evaluate number of reconfiguration failure due the transmission
• Check M1005C128 CANC_ADD_SRNC_TRAN_STP_FAIL
• Check M1001C531-C533 RAB_STP_FAIL_XXX_IUB_AAL2

5. If high SCC_FAILED_due_to_Others
• Check RNC internal transport resources usage (DMPG)
• Require ICSU troubleshooting

51 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
Example: SCC Success and attempts

52 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
Call/Session Drop monitoring & analysis
Example: HSDPA SCC Failures

Failures due transmission

53 RN3705EN50GLA0 © Nokia Solutions and Networks 2015


This page contains no comments
54
27
.0
7
27 .20
.0 09
7
28 .20 __
.0 09 15
7 :
28 .20 __ 00:

0.00
10.00
20.00
30.00
40.00
50.00
60.00
.0 09 19 00
7 . _ :0
28 20 _ 0:
.0 09 00 00
7 :
28 .20 __ 00:
.0 09 08 00
7 . _ :0
28 20 _ 0:
.0 09 12 00
7 :
29 .20 __ 00:
.0 09 16 00
7 . _ :0
29 20 _ 0:
.0 09 21 00
7 :
29 .20 __ 00:
.0 09 01 00
7 . _ :0
29 20 _ 0:
.0 09 08 00
7 :
29 .20 __1 00:
.0 09 3: 00
7. _ 0
30 20 _ 0:
.0 09 17 00
7 :

HSUPA congestion control example –RU10


30 .20 __ 00:
.0 09 21 00
7 . _ :0

RN3705EN50GLA0
30 20 _ 0:
.0 09 01 00
7 :
30 .20 __ 00:
Call/Session Drop monitoring & analysis

.0 09 11 00
7 :
30 .20 __ 00:
.0 09 15 00
:

IUB_DELAY_CC_DELAY_IND_(M1022C69)
7
31 .20 __ 00:
.0 09 19 00
7 :

IUB_LOSS_CC_FRAME_LOSS_IND_(M1022C71)
31 .20 __ 00:

HW_OVERL_CC_FRAME_LOSS_IND_(M1022C73)
.0 09 23 00
7 :
31 .20 __ 00:
.0 09 10 00
7 . _ :0
01 20 _ 0:
.0 09 15 00
8 :
01 .20 __ 00:
.0 09 19 00
8 . _ :0
01 20 _ 0:
.0 09 00 00
8 :
01 .20 __ 00:
.0 09 09 00
8 . _ :0
02 20 _ 0:
.0 09 13 00
8 :
02 .20 __ 00:
.0 09 17 00
8 . _ :0
02 20 _0 0:
.0 09 1: 00
8

© Nokia Solutions and Networks 2015


02 .20 __ 00:
.0 09 13 00
8 :
03 .20 __ 00:
.0 09 17 00
8 . _ :0
03 20 _ 0:
.0 09 21 00
8 . _ :0
20 _0 0:

HW_OVERL_CC_DELAY_IND_(M1022C70)
09 8: 00
__ 00
12 :00
:0
0:

IUB_DELAY_CC_FRAME_LOSS_IND_(M1022C72)
00
This page contains no comments
RN3705EN50GLA0 © Nokia Solutions and Networks 2015
This page contains no comments