3G KPI Optimization Sheet(Nokia)

(1)

Jump/Network Operations Portal NOP (intranet)

Good methodology is to list top 10-20 worst cells per region and to build and follow an action plan on those –Includes counters, KPIs and also reports in Reporting Suite

–http://nop-i.nokia.com/docs/jump.htm

•Almost all data has to be analysed at WCELL or WBTS level for the worst cells -> Evaluation over time and Comparison between large areas (Cities, RNCs) is still required –Cell Availability

–Failures due to Radio, BTS or transport –Handover Performance

–Traffic

–Cell Resources –Iub Signalling

•Some data is better analysed at RNC level->Here only the time evolution and RNC comparison is useful –Failures due the RNC, Iu, Iur

–Iur, Iu, Relocation Signalling

Monitor Cell/Neighbour cells Availability - missing cell has impact to neighbouring cells performance also

1. Assess weekly average PLMN KPI performance to identify KPIs below targets –Start from bigger picture assessment (PLNM -> RNC -> Cluster -> WCEL )

–Weekly average will smooth the performance and gives better accuracy of performance assessment as daily performance varies a lot especially in unloaded network, gives more accurate picture of KPIs. 2. Assess network performance at RNC/Area level to check if bad performance happens across network or only particular RNC/Area

–Compare different RNC/Regions Performance

3. Apply drill down approach to assess bad performing KPIs in WCEL level –Identify the failure call phases

–Categorizing failure ratio or distribution of each counters (Radio, transmission, BTS, RNC) –Identify main cause of underperforming KPI’s

4. Prioritize analysis

–Filter using high number of failures or high number failure ratio (weighting) –Identify top 20/50 worst cells

5. Analyze failure distribution in the network topology (rural, RNC border, expressway) 6. Propose Solution for cells having network KPIs below KPI targets

Because of the large number of cells in the network, it is not feasible to analyse all the cells. •This required a part-time or dedicated tracking role

(2)

Either total number of failures or failure rate (%) could be used

In Loaded networks the Weekly Busy Hour CSSR is relevant

In cell level it is needed to compute BH statistic based on absolute time period (e.g. 16-18h every day)

Typically CS and PS busy hours does not exist in the same time During weekend CS data drops significantly while PS data is quite constant

The new smart phones such as Blackberry (RIM), iPhone (Apple) and N97 (Nokia) are loading the network in a new way Fast dormancy or Quick Release will have impact to the load & performance

Call can be traced by using subscriber's IMSI, MSISDN or equipment’s IMEI number Subscriber trace can be used for:

•Coverage hole, missing neighbour or capacity problem

• The failures originate mostly from congestions (Iub, BTS HW (CEs), radio) • The call blocking probability is designed for the BH

In Unloaded networks the Weekly Busy Hour CSSR may not yield the hour with highest blocking as NRT traffic is taken in the account as well as RT traffic

•In example below, the PS Busy Hour is later in the evening (20-21 hours) than CS (15-16 hours).

•Applications which require ‘always on’ connectivity have become very popular in many networks

(3)

Jump User Id: Jump password:

-> Evaluation over time and Comparison between large areas (Cities, RNCs) is still required

Weekly average will smooth the performance and gives better accuracy of performance assessment as daily performance varies a lot especially in unloaded network, gives more accurate picture of KPIs. Assess network performance at RNC/Area level to check if bad performance happens across network or only particular RNC/Area

(4)

(5)

(6)

(7)

CS/PS Access Failure Optimization:

Call Setup analysis

Call Setup Success Rate (CSSR)

1.1.1.1.1. Accessibility Analysis (CS/PS/HS)

(8)

Poor CSSR could be a result of

Voice Access failure= RRC Setup & Access fails + RAB Setup & Access fails

Starting criteria for setup failure analysis

b) Interference-- best server Ec/No should not be less than -12db

Tilt- for Dominance Optimization

Missing neighbor checks-- for neighbor optimization

4) RRC Connection Setup Received?

NO---a) RRC Setup reject msg. received---No (Check failure Cause)

RRC Setup fails occurs (due to HC, AC, BTS, frozen BTS, Transp, Iub AAl2 fails, RNC, RNTI & ICSU fails)--- then sends RRC connection setup reject msg. RRC_CONN_STP_FAIL_HC (very Minor)--- usually 0%

RRC_CONN_STP_FAIL_AC (dominant)

RRC_CONN_STP_FAIL_TRANS

For ATM based Iub

•Poor coverage or dominance or interference issues in Radio interface

•Capacity issues in Radio or Iub interface

•Configuration issues in WBTS (parameters or HW)

1) Site Ok?-- Cell Availability(Cell level report-RSRAN001), Alarms/HW Issues

2) Coverage or Interference-- Cell Power Report

a) Coverage-- best server RSCP should not be lesser than -102dbm--- Coverage Optimization--

3) AICH ACK. Received?----No (UL Coverage & RACH parameter Optimization)

Yes (AC Optimization--- check PRx Noise & Interferer Around BTS)

•Check UL Interference (R99 Noise Rise, RTWP- Cell Power Report), DL Power (HSDPA, R99 power) & Code occupancy if there is need to upgrade radio capacity-- [ HSPA no. of Users ] Cell Utilization/capacity Report •UL Power Spikes -> Disable UL Admission Control to if the number of failures is critical (PrxTarget-> 30 dB), implement TN159

RRC_CONN_STP_FAIL_BTS (dominant when HSDPA active)

•Check BTS configuration in terms of CE allocation – Use Channel Element (M5001) Counters in order to evaluate lack of Channel Elements-- NodeB Utilization/CE Utilization Report •Evaluate NBAP counters (radio link reconfiguration failures)-- NBAP Signalling Per cause Report

•Expand the Capacity or decrease the traffic offered to the site--- Check Uplink CE Usage(should not be >80-85%--- NodeB Utilization/CE Utilization Report) •Frozen BTS/BTS not responding-- delete and re-create COCO/Site Reset

•Evaluate Number of reconfiguration failure due the transmission-- Traffic_on_Physical_Medium_Sub-Layer & Iub Capacity reports •Expand the capacity or decrease the traffic offered to the site

•Check COCO Configuration

•Use AAL2 Multiplexing in case of two WAM

For IP based Iub---•Check IP based route parameters (ZQRL;)/ IP_Route_Resource_Reservations Report

(9)

RRC_CONN_STP_FAIL_RNC

RRC_CONN_STP_FAIL_ICSU_OVERL

RRC_CONN_STP_FAIL_RNTI ALLO FAIL

b) c)

RRC Access failure reasons: RRC Active release can be due to-- ISHO, IFHO, SRNC Relocation, Pre-emption

Coverage or interference-- Cell Power Report

RRC_CONN_ACC_FAIL_MS

Some more counters of RRC Access fails

RRC CONN REJECT DUE TO IUB OVERLOAD CTRL RRC CONN REJECT DUE TO MAX REGISTRATIONS

RRC CONN REJECT DUE TO CENTRALIZED UNIT OVERLOAD RRC CONN REJECT DUE TO BUFFER LIMIT CTRL

RRC CONN REJECT DUE TO RNC RESTART SHO Branch setup fails BTS/Iub-- SHO Overhead Report--No. 88, traffic

RNC capacity SW New DSP counters-- DSP Resource Usage, DSP State Changes- System reset/user reset & DSP_Service_Statistics reports

•Typically RNC fault or Incoming SRNC Relocation Failure (inter-RNC border)--- RNSAP/NBAP Signalling •Iur Troubleshooting-- RNSAP_Signalling Report

•DMPG problem in RNC

•Required ICSU log tracing if no RNC fault or SRNC relocation problem

•ICSU overload

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

YES---RRC Connection Setup complete msg. sent from UE?---No (L1 Synchronization Fail/ RNC Internal failures)-- RRC Access fails YES ( RRC Active fails-- a) Radio

Fails---RRC_CONN_ACC_FAIL_RADIO (Dominant failure cause type) • Perform drive test to detect if UL or DL coverage

–UL Coverage

§UL coverage(TMA/MHA chk), Interference-- Tilt / Missing Neighbor chk / best server Ec/No should not be less than -12db

–DL Coverage

§Tune SCCPCH Power if UE does not receive the RRC Setup Message from RNC./ Antenna tilt(CPICH RSCP should not be<-102dbm) / / Coverage Optimization-- PRACH_Propagation_Delay Report

• If UE does not synchronize(L1)

–tune CPICHToRefRABOffset vs.Qqualmin (or Qrxlevmin)

–Due to Increased interference with HSDPA, this max radio link power for AMR (offset parameter) has been increased (0-> -2 dB->-4 for networks with lot of smartphones)

–UL Coverage

§Tune Cell Dominance (or CPICH) in order to balance UL and DL (if UL interference is not the cause) If RRC setup/access failure due to Radio/MS, it is also possible to check whether UEs are located at distance area or close to cell edge area

•Propagation delay counters from RRC measurement M1006C128-C148 reports call setup distance during RRC connection request or cell update

•This give hints that either cells has large coverage area (tall sites with over-shooting) or non-optimum cell coverage from neighbouring cells

•M1006C203 •M1006C204 •M1006C205 •M1006C206 •M1006C208

(10)

RAB Setup fails occurs (due to AC, BTS, frozen BTS, Transp, Iur Trans, Iu-CS Trans, Iub AAl2

fails)---then RNC sends RANAP: RAB Assignment Response msg. to CN, sending appropriate failure cause.

RAB Access fails occurs (due to UE & RNC

fails)---UE sends RB setup failure msg. to RNC, RNC sends RAB Assignment response to CN, + Iu release request to CN

RAB Active fails occurs (due to Radio, Iu, Iur, Iub, RNC internal

fails)---RAB setup & Access Fail Root Cause Analysis

RAB_CONN_STP_FAIL_AC (dominant) [ Admission control could reject establishment of new Connection/bearer ]

RAB_CONN_STP_FAIL_TRANS

For ATM based Iub

RAB_CONN_STP_FAIL_RNC

Yes---RAB Setup failure received?---No ( chk failure cause)

Yes (chk failure cause--Not Radio related Problem/Cell Update)

•Check UL Interference (R99 Noise Rise, RTWP- Cell Power Report), DL Power (HSDPA, R99 power) & DL Code occupancy if there is need to upgrade radio capacity-- [ HSPA no. of Users ] Cell Utilization/Capacity Report •UL Power Spikes -> Disable UL Admission Control to if the number of failures is critical (PrxTarget-> 30 dB), implement TN159

•When HSPA is enabled in the cell, the DL and UL resources are shared between HSPA and R99 users

–Both R99 and HSPA should be monitored-- Cell utilization + Allocated_Traffic_Amounts_(R99_+_HSPA) report

–From the HSDPA side, besides of blocking, HSDPA throughput limitations can be also monitored-- Node B utilization/ HSPA Overview/ RAB_CONN_STP_FAIL_BTS (dominant when HSDPA active)

•Check BTS configuration in terms of CE allocation – Use Channel Element (M5001) Counters in order to evaluate lack of Channel Elements-- NodeB Utilization/CE Utilization Report •Evaluate NBAP counters (radio link reconfiguration failures)-- NBAP Signalling Per cause Report

•Expand the Capacity or decrease the traffic offered to the site--- Check Uplink CE Usage(shouls not be >80-85%--- NodeB Utilization/CE Utilization Report) •Frozen BTS/BTS not responding-- delete and re-create COCO/Site Reset

•Evaluate Number of reconfiguration failure due the transmission-- Traffic_on_Physical_Medium_Sub-Layer & Iub Capacity reports •Expand the capacity or decrease the traffic offered to the site

•Check COCO Configuration

•Check RAB_STP_FAIL_XXX_IUB_AAL2, M1001C531-C533

•Use AAL2 Multiplexing in case of two WAM

For IP based Iub---•Check IP based route parameters (ZQRL;)/ IP_Route_Resource_Reservations Report

DCH Reconfiguration failures due to AC/BTS/Trans-- NRT_DCH_Allocations_Statistics report SHO Branch setup fails BTS/Iub-- SHO Overhead Report--No. 88, traffic

RNC capacity SW New DSP counters-- DSP Resource Usage, DSP State Changes- System reset/user reset & DSP_Service_Statistics reports

•Typically RNC fault or Incoming SRNC Relocation Failure (inter-RNC border)--- RNSAP/NBAP Signalling •Iur Troubleshooting-- RNSAP_Signalling Report

(11)

RAB_CONN_STP_FAIL_ICSU_OVERL

RAB_CONN_STP_FAIL_RNTI ALLO FAIL

RAB_ACC_FAIL_XXX_MS

Packet Service & Session [ PS ]

Packet calls starts with user plane capacity allocation (transfer from FACH/PCH, DCH 0/0) and ends with dedicated resource release (transfer back to FACH/PCH, DCH 0/0, RAB release, outgoing relocation, HHO, ISHO) There are counters for the following channel combinations

DL = DCH UL = DCH

DL = HS-DSC UL = DCH

DL = HS-DSC UL = E-DCH

AC, BTS, Frozen BTS, RNC, ANCH fails

•Required ICSU log tracing if no RNC fault or SRNC relocation problem

•ICSU overload

• RNC decides to reject RRC connection request due to RNTI allocation failure caused by RRMU overload RAB_ACC_FAIL_Iur trans--- RNC capacity Report

RAB_ACC_FAIL_IuCS trans--- IuCS Report(94)

RAB_ACC_FAIL_Iub AAl2 fails--- •Check RAB_STP_FAIL_XXX_IUB_AAL2, M1001C531-C533, •Use AAL2 Multiplexing in case of two WAM, Iub Capacity report, NRT_Radio_Bearer_stats--AAl2 congestion

•Evaluate Cell resource Prx and Ptx (for example high uplink interference)--NRT_Radio_Bearer_stats report for Prx & Ptx ratio •Check RB reconfiguration failure ratio ( If ATO setting is insufficient , rec. 500ms)--- RRC signalling report

RRC_CONN_ACC_FAIL_RADIO (Dominant failure cause type)

• Perform drive test to detect if UL or DL coverage –UL Coverage

–DL Coverage

§Tune SCCPCH Power if UE does not receive the RRC Setup Message from RNC./ Antenna tilt(CPICH RSCP should not be<-102dbm) / / Coverage Optimization-- PRACH_Propagation_Delay Report

Packet Service - A call with RABQoS parameters: Traffic Class = Interactive or Background.

•The RRC setup has been done with cause codes: MOC Interactive, MTC Interactive, MOC Background or MTC Background.

Packet Session - A call with RAB/RB QoS parameters: Traffic Class = Interactive or Background.

•Here a call refers to the DCH/HS-DSCH/E-DCH live time, that is, the time the session is active for traffic.

•The RRC setup has been done with cause codes: MOC Interactive, MTC Interactive, MOC Background or MTC Background.

•Rel99

•HSDPA •There could be multiple packets inside single RAB

•HSUPA • RU20 introduce Direct resource allocation for HSPA

(12)

UE, RNC fails

Initial Setup fail procedure

(DSP resource usage/ DSP state changes/ DSP service statistics reports)- hardware

•Other Failures

HSDPA

Packet Session RAB Access

Failures

Packet Session

Setup Failures (R99)

•AC failure : lack of DL power or high UL interference •BTS failure: lack of HW capacity

•DMCU failure: lack of DSP resources in RNC

•TRANS failure: lack of Iub capacity (COCO parameters) •UE failure: UE internal problem (not capability issue)

(13)

(14)

HSUPA

(15)

(16)

(17)

PrxNoise value between -99.5 dBm and -103.5 dBm. In Tmo=-105dbm(Nokia default=-105dbm) RRC Setup fails occurs (due to HC, AC, BTS, frozen BTS, Transp, Iub AAl2 fails, RNC, RNTI & ICSU fails)--- then sends RRC connection setup reject msg.

Example

Coverage Optimization--

PRACH_Propagation_Delay Report

--- check PRx Noise & Interferer Around BTS)

DL Power (HSDPA, R99 power) & Code occupancy if there is need to upgrade radio capacity-- [ HSPA no. of Users ] Cell Utilization/capacity Report (PrxTarget-> 30 dB), implement TN159

Channel Element (M5001) Counters in order to evaluate lack of Channel Elements-- NodeB Utilization/CE Utilization Report Check Uplink CE Usage(should not be >80-85%--- NodeB Utilization/CE Utilization Report)

Short One day dat-- to show top 10 sites having highest number of BTS failures

Traffic_on_Physical_Medium_Sub-Layer & Iub Capacity reports •Majority of BTS Failures is coming from few sites.

•Check CE usage for these sites - > add CE capacity if needed or try to reduce the usage One site detail analysis show that Average UL CE usage ratio is above 90% causing high blocking -> Capacity issue

(18)

Ue fails---

RRC Active release can be due to-- ISHO, IFHO, SRNC Relocation, Pre-emption

Missing neighbor checks-- for neighbor optimization DSP Resource Usage, DSP State Changes- System reset/user reset & DSP_Service_Statistics reports

RNSAP/NBAP Signalling

(L1 Synchronization Fail/ RNC Internal failures)-- RRC Access fails YES ( RRC Active fails-- a) Radio

Fails---RNC Internal fails

--Missing Neighbor chk / best server Ec/No should not be less than -12db

if UE does not receive the RRC Setup Message from RNC./ Antenna tilt(CPICH RSCP should not be<-102dbm) /

Due to Increased interference with HSDPA, this max radio link power for AMR (offset parameter) has been increased (0-> -2 dB->-4 for networks with lot of smartphones)

Cell Dominance (or CPICH) in order to balance UL and DL (if UL interference is not the cause)

UEs are located at distance area or close to cell edge area

from RRC measurement M1006C128-C148 reports call setup distance during RRC connection request or cell update This give hints that either cells has large coverage area (tall sites with over-shooting) or non-optimum cell coverage from neighbouring cells

•

(19)

RAB Setup fails occurs (due to AC, BTS, frozen BTS, Transp, Iur Trans, Iu-CS Trans, Iub AAl2

fails)---then RNC sends RANAP: RAB Assignment Response msg. to CN, sending appropriate failure cause.

UE sends RB setup failure msg. to RNC, RNC sends RAB Assignment response to CN, + Iu release request to CN

[ Admission control could reject establishment of new Connection/bearer ]

Number_of_HSPA_Users_and_UE_capability/ MAC-hs_Retransmissions_by_Code_and_Modulation_Usage reports

i.e. (The number of cancelled synchronised radio link reconfigurations on SRNC side due to a transmission setup failure or RNC DMPG/DSP resource allocation)

Not Radio related Problem/Cell Update)

DL Power (HSDPA, R99 power) & DL Code occupancy if there is need to upgrade radio capacity-- [ HSPA no. of Users ] Cell Utilization/Capacity Report (PrxTarget-> 30 dB), implement TN159

When HSPA is enabled in the cell, the DL and UL resources are shared between HSPA and R99 users

Cell utilization + Allocated_Traffic_Amounts_(R99_+_HSPA) report

, HSDPA throughput limitations can be also monitored-- Node B utilization/ HSPA Overview/

Channel Element (M5001) Counters in order to evaluate lack of Channel Elements-- NodeB Utilization/CE Utilization Report Check Uplink CE Usage(shouls not be >80-85%--- NodeB Utilization/CE Utilization Report)

•Check M1005C128 CANC_ADD_SRNC_TRAN_STP_FAILfailure)

Traffic_on_Physical_Medium_Sub-Layer & Iub Capacity reports

IP based route parameters (ZQRL;)/ IP_Route_Resource_Reservations Report

DSP Resource Usage, DSP State Changes- System reset/user reset & DSP_Service_Statistics reports

(20)

Missing neighbor checks-- for neighbor optimization

Packet calls starts with user plane capacity allocation (transfer from FACH/PCH, DCH 0/0) and ends with dedicated resource release (transfer back to FACH/PCH, DCH 0/0, RAB release, outgoing relocation, HHO, ISHO)

RAB_STP_FAIL_XXX_IUB_AAL2, M1001C531-C533, •Use AAL2 Multiplexing in case of two WAM, Iub Capacity report, NRT_Radio_Bearer_stats--AAl2 congestion

NRT_Radio_Bearer_stats report for Prx & Ptx ratio –UL Coverage tuning

RRC signalling report §Tune Cell Dominance (or CPICH) if the cause is UL interference –DL Coverage tuning

§Tune SCCPCH Power if UE does not receive the RRC Setup Message from RNC.

Missing Neighbor chk / best server Ec/No should not be less than -12db

if UE does not receive the RRC Setup Message from RNC./ Antenna tilt(CPICH RSCP should not be<-102dbm) /

The RRC setup has been done with cause codes: MOC Interactive, MTC Interactive, MOC Background or MTC Background. session is active for traffic.

The RRC setup has been done with cause codes: MOC Interactive, MTC Interactive, MOC Background or MTC Background.

There could be multiple packets inside single RAB RU20 introduce Direct resource allocation for HSPA

(21)

(DSP resource usage/ DSP state changes/ DSP service statistics reports)- hardware

Now -- check schedular type: 16 users/cell, 64 users/cell, shared schedular/ full baseband schedular

Wrong scheduler type may cause HSDPA setup problems due to too many users, or waste baseband capacity if schedulers are underutilized. Can cause High HS-DSCH set up fails during busy hrs due to max users reached.

SHO Overhead chk--- cell level report--should be nearly 40%. Software bugs in BTS hardware with some features.

RNC, BTS, Iub, UE, UL-DCH, Multi-RAB, Max. users, DL Pwr limits. 1. If high HSDPA Access Failure _too many HSDPA users --

§Check simultaneous HSDPA users--- Number_of_HSPA_Users_and_UE_capability report

§DCH selected due to too many HSDPA users, RNC_660b---- Number_of_HSPA_Users_and_UE_capability report Schedular type defined in WBTS commissioning parameter--- as HSDPA shared schedular type license

•If shared scheduler is used, the number of schedulers depend on Tcell parameter settings on the site.

2. If high HSDPA Access Failures_UL DCH (RNC_661c/d)

§Rejected HS-DSCH return channel due to lack of UL radio resources

Check--RSRAN071_-_Utilization_Shares_of_Total_Traffic_Allocation_Amounts report-- for HS-DSCH return chn bitrate utilization(16,64,128,384)

§Monitor UL load --chk UL power congestion ( lack of radio resource for UL return channel)-- cell capacity report

3. If high HSDPA Access Failure_UE

§Check RB reconfiguration failure rate-- terminal problem-- RRC signalling report §ICSU log for UE types troubleshooting ?

4.If high HSDPA Access Failure_BTS

§Lack of UL channel resources (check CE resource utilisation using M5001 counters at BH)

(22)

6. HSDPA setup fail due RNC internal reason

5. HS-DSCH return channel setup fail due to Iub transport –Breakdown the failure distribution (64,128,384,MAC-d)

–Evaluate number of reconfiguration failure due the transmission-- RRC signalling report –Check M1005C128 CANC_ADD_SRNC_TRAN_STP_FAIL

–Check RAB_STP_FAIL_XXX_IUB_AAL2, M1001C531-C533

–Check RNC Unit load (DMPG) –Max number of users/RNC –DSP failures and faulty alarms

(23)

If HSDPA setup is failing also HSUPA setup will fail, but it could be also that only HSUPA will fail. The reasons are similar to HSDPA E-DCH Setup FR due to BTS (RL reconfiguration failure to RNC)

RN RN

RN E-DCH Setup FR due to Other Failures (RNC internal reason) Also there could be too many HSUPA users

RN UL DCH Selected due to too many HSUPA users HSUPA setup failed due to BTS reports HSUPA cannot be allocated

RN

M1000C268-C270 – These counters measure the BTS HW limitation during HSUPA Calls EDCH cannot be allocated in case HSUPA is not supported in SHO branch

E-DCH Allocation FR due to Not Acceptable Active Set RNC, BTS, Max. users, UE, E-DCH not selected due to too many hsupa users, AC Fails.

RNC_956a

E-DCH Setup FR due to Transport (RL reconfiguration cancel from RNC)

E-DCH Setup FR due to UE (RB reconfiguration failure from UE)--terminal problem-- RRC signalling report

E-DCH Not Selected due the BTS HW (BTS sent radio resource measurement report)

RNC_1103a

For static resource allocation the power could limit

(24)

(25)

(26)

PrxNoise value between -99.5 dBm and -103.5 dBm. In Tmo=-105dbm(Nokia default=-105dbm)

Cell Utilization/capacity Report

Short One day dat-- to show top 10 sites having highest number of BTS failures Majority of BTS Failures is coming from few sites.

Check CE usage for these sites - > add CE capacity if needed or try to reduce the usage

(27)

(28)

Setup Failures due Admission Control - AC

Number_of_HSPA_Users_and_UE_capability report

Number_of_HSPA_Users_and_UE_capability/ MAC-hs_Retransmissions_by_Code_and_Modulation_Usage reports

i.e. (The number of cancelled synchronised radio link reconfigurations on SRNC side due to a transmission setup failure or RNC DMPG/DSP resource allocation)

Cell Utilization/Capacity Report

•RRC/RAB cs setup failures due AC - Admission control rejects the establishment of new RRC/RAB connection due the

–UL Power, DL Power and DL Codes

•RAB PS setup failures due AC – Admission control rejects the establishment of new PS radio bearer due the

–UL power, DL Power, DL codes and too many users in the scheduler

•HSDPA Access failures due the UL DCH – AC rejects the establishment of new HSDPA connection (related to HSDPA UL return channel)

–UL power

•HSDPA access failures due number of HSDPA users reached – new HSDPA connection is rejected due too many HSDPA users

(29)

Missing neighbor checks-- for neighbor optimization –UL Coverage tuning

§Tune Cell Dominance (or CPICH) if the cause is UL interference –DL Coverage tuning

(30)

Now -- check schedular type: 16 users/cell, 64 users/cell, shared schedular/ full baseband schedular

Wrong scheduler type may cause HSDPA setup problems due to too many users, or waste baseband capacity if schedulers are underutilized. Can cause High HS-DSCH set up fails during busy hrs due to max users reached.

SHO Overhead chk--- cell level report--should be nearly 40%. Software bugs in BTS hardware with some features.

If high HSDPA Access Failure _too many HSDPA users --

Check simultaneous HSDPA users--- Number_of_HSPA_Users_and_UE_capability report

DCH selected due to too many HSDPA users, RNC_660b---- Number_of_HSPA_Users_and_UE_capability report Schedular type defined in WBTS commissioning parameter--- as HSDPA shared schedular type license

, the number of schedulers depend on Tcell parameter settings on the site.

If high HSDPA Access Failures_UL DCH (RNC_661c/d)

Rejected HS-DSCH return channel due to lack of UL radio resources

Check--RSRAN071_-_Utilization_Shares_of_Total_Traffic_Allocation_Amounts report-- for HS-DSCH return chn bitrate utilization(16,64,128,384)

--chk UL power congestion ( lack of radio resource for UL return channel)-- cell capacity report

Check RB reconfiguration failure rate-- terminal problem-- RRC signalling report ICSU log for UE types troubleshooting ?

Lack of UL channel resources (check CE resource utilisation using M5001 counters at BH)

(31)

6. HSDPA setup fail due RNC internal reason

5. HS-DSCH return channel setup fail due to Iub transport Breakdown the failure distribution (64,128,384,MAC-d)

Evaluate number of reconfiguration failure due the transmission-- RRC signalling report Check M1005C128 CANC_ADD_SRNC_TRAN_STP_FAIL

(32)

If HSDPA setup is failing also HSUPA setup will fail, but it could be also that only HSUPA will fail. The reasons are similar to HSDPA E-DCH Setup FR due to BTS (RL reconfiguration failure to RNC)

E-DCH Setup FR due to Other Failures (RNC internal reason) UL DCH Selected due to too many HSUPA users

HSUPA setup failed due to BTS reports HSUPA cannot be allocated

M1000C268-C270 – These counters measure the BTS HW limitation during HSUPA Calls EDCH cannot be allocated in case HSUPA is not supported in SHO branch

E-DCH Allocation FR due to Not Acceptable Active Set

E-DCH Setup FR due to Transport (RL reconfiguration cancel from RNC)

E-DCH Setup FR due to UE (RB reconfiguration failure from UE)--terminal problem-- RRC signalling report

E-DCH Not Selected due the BTS HW (BTS sent radio resource measurement report)

(33)

(34)

(35)

(36)

(37)

Setup Failures due Admission Control - AC

•RRC/RAB cs setup failures due AC - Admission control rejects the establishment of new RRC/RAB connection due the

–UL Power, DL Power and DL Codes

•RAB PS setup failures due AC – Admission control rejects the establishment of new PS radio bearer due the

–UL power, DL Power, DL codes and too many users in the scheduler

•HSDPA Access failures due the UL DCH – AC rejects the establishment of new HSDPA connection (related to HSDPA UL return channel)

–UL power

(38)

(39)

(40)

(41)

(42)

(43)

(44)

(45)

(46)

- Admission control rejects the establishment of new RRC/RAB connection due the – Admission control rejects the establishment of new PS radio bearer due the

– AC rejects the establishment of new HSDPA connection (related to HSDPA UL return channel) HSDPA access failures due number of HSDPA users reached – new HSDPA connection is rejected due too many HSDPA users

(47)

(48)

(49)

(50)

(51)

(52)

Voice Drop Call Optimization:

Check core network parameter setting if RAB_ACT_FAIL_XXX_IU Check SCCP SGSN/RNC IuPS Tias/Tiar if RAB_ACT_FAIL_BACKG_IU

-- Check if any BTS faulty alarm (7651, 7653, 7654 alarm)

1.1.1.1.1. Retainibility Analysis (CS/PS/HS)

1. Monitor Daily Performance Reports/KPIs Worksheet---Pick Worst Offenders

2. Identify DCR top offenders…. few cells?…. Any particular area ? Known Coverage issue? Need a new site ? 3. check cell & its neighbor cells availability (availability should be 100%)---- cell level report

4. Check current alarms on the site / sector & same for neighbor cells?--- alarm history especially for transmission issues (NBAP link failures/T1 fluctuations?) 6. Check if the sector is dropping the calls due to RF (Radio fails)-- Not RF(Iu, Iur, BTS, RNC, MS, CIPH, UE, trans fails)

7. If not RF, check :

• Voice Drops due to Iu

• Voice Drops due to Iur

RAB_ACC_FAIL_Iur trans--- RNC capacity Report

• Voice Drops due to BTS

•If No alarms-- delete and re-create COCO/COCO reset/Site Reset---may be due to Frozen BTS/BTS not responding •Evaluate NBAP counters (radio link reconfiguration failures)-- NBAP Signalling Per cause Report

•Expand the Capacity or decrease the traffic offered to the site--- Check Uplink CE Usage(shouls not be >80-85%--- NodeB Utilization/CE Utilization Report) • Voice Drops due to RNC

•Typically RNC fault or Incoming SRNC Relocation Failure (inter-RNC border)--- RNSAP/NBAP Signalling

RNC capacity SW New DSP counters-- DSP Resource Usage, DSP State Changes- System reset/user reset & DSP_Service_Statistics reports •Iur Troubleshooting-- RNSAP_Signalling Report

•Required ICSU log tracing if no RNC fault or SRNC relocation problem •ICSU overload

• RNC decides to reject RRC/RAB connection RRMU overload, priority calls during Busy hrs • Voice Drops due to UE

–Check physical channel reconfiguration failure rate (IFHO, ISHO, code optimisation)

•Evaluate Cell resource Prx and Ptx (for example high uplink interference)--NRT_Radio_Bearer_stats report for Prx & Ptx ratio •Check RB reconfiguration failure ratio ( If ATO setting is insufficient , rec. 500ms)--- RRC signalling report

• Voice Drops due to CIPH • Voice Drops due to Trans RAB_ACC_FAIL_Iur trans--- RNC capacity Report RAB_ACC_FAIL_IuCS trans--- IuCS Report(94)

RAB_ACC_FAIL_Iub AAl2 fails--- •Check RAB_STP_FAIL_XXX_IUB_AAL2, M1001C531-C533, •Use AAL2 Multiplexing in case of two WAM, Iub Capacity report, NRT_Radio_Bearer_stats--AAl2 congestion

7. If drops are due to RF (Voice Drops due to Radio fails), check the Site location, Neighbors, Cell to cell HO stats(SHO,IFHO,ISHO), PRACH delay distance and Ec/No quality distribution statistics















1 _____

____

%100_

LinksRadioServerBestofNumber

LinksRadioofNumberTotal

OverheadSHO

(53)

Need Tilt / Azimuth change to improve the area?

Yes-- (check Iur capacity and SRNC relocation problem)

No-- SHO_Adjacencies(46)--neighbor add/delete, Soft_Handover_Performance(28), Active_Set_Size_for_NRT-RT_Traffic--active set update fails-- check ad/delete/replacement window

Check SHO Overhead (RNC_79b) to see how big is SHO area, if it is too small SHO may fails and if too big capacity is wasted

If SHO KPI> 90%-- check ISHO failures?

No ISHO failures--- new site needed?/ RF & IFHO Neighbor Optimization Yes ISHO failures (ISHO

Reports)---Coverage_Quality_ISHO_Performance_per_Cause reports--- UL DCH qual, UE tx pwr, DL DPCh, RSCP/EcNo, IMSI, Emergency drops, PRx total, PTx Total, drops due to service based HO GSM frequency plan neighbour RNC and MSC database consistency audit( for BCCh/BSIC collision)

check alarm of reference clock in 3G or in 2G, check 2G TCH congestion

If No cell found ratio is>90% & enough ADJIs--- Wrong reference Clock tuning( 10MHz tunning)

TCH Blocking/TCH congestion/TCH failures/2G traffic/2G coverage & Interference –UL Coverage

–DL Coverage

§Tune SCCPCH Power if UE does not receive the RRC Setup Message from RNC./ Antenna tilt(CPICH RSCP should not be<-102dbm) / / Coverage Optimization-- PRACH_Propagation_Delay Report ( Cell range in TMO Sites-20Kms)

9. HO issue/HO fails? All Neighbor Exists? SHO….ISHO……IFHO…….?? Neighbor Add/delete? Check SHO KPI if performance < 90% ( leads to Radio failure)--- Yes

–Check if cells are at RNC border

–Detect badly performing neighbours using HO success rate per adjacency counters-- delete/create them again, check SHO Overhead

–High incoming HO failure rate in all ADJS – check sync alarms

–Audit Adjacent sites for Alarms/capacity/traffic and visualization check with map –Evaluate HO control parameters and trigger threshold

Check No cell found ratio>40% or not?-- Inter-System_Handover_Performance report

If No cell found ratio >40%-- 3G cell at inter-RNC border/ 3G cell covers a coverage hole---- RF & ISHO neighbor optimization –Check missing neighbour/badly performing neighbors(ISHO Adjacencies report),

4.Check ISHO KPI if RT ISHO < 90% or NRT < 80% (leads to radio failure)

If No cell found ratio<40% & ISHO Success rate<90%--- Investigate 2G

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)















1 _____

____

%100_

LinksRadioServerBestofNumber

LinksRadioofNumberTotal

OverheadSHO

      _   1 _ _ _ _ _ _ _ _ _ % 100 _ Links Radio Server Best of Number Links Radio of Number Total Overhead SHO

(54)

RRC active drops reasons: RAB AMR active drops reasons: Iu Iu Iur Iur BTS RNC RNC MS MS UE

CIPH Ciphering Trans

UE Radio fails

Trans

Radio fails

R99 PS Drop Call Optimization: R99 is NRT service basically

PSSR rate can be monitored separately for R99, HSDPA and HSUPA

Packet Session Analysis

Packet call normal releases (normal end of the call) counters includes

10. It might be observed on some sites that although there is no alarm and cell is carrying traffic, some HW faults ( could be found only during the site visits) causing call drops e.g. bad feeder or antenna or MHA problem?

• Transition to DCH 0/0, Cell_FACH or Cell_PCH due to inactivity or low utilisation • Outgoing SRNC relocation

• Inter-RNC hard handover















1 _____

____

%100_

LinksRadioServerBestofNumber

LinksRadioofNumberTotal

OverheadSHO

(55)

Packet call Failures are divided into

ATO=Offset for activation time of SRBs on HSPA= 300 to 500ms Ptx target=40dbm

Prxtarget=5dbm

CPICH tx power= 35.1dbm

Check NBAP RL reconfiguration failure rate?

NBAP_Signalling report-- Radio link - SRNC, Radio link - DRNC, RL setups/reconf fails for HSDPA MAC-d flow

NBAP_Signaling_per_cause report--- RL setup for an RRC connection-Fail, BTS not respond, RL operations- RL fails(SRNC,DRNC), RL setup for HO failures, SRNC/DRNC(SHO/HHO-BTS not respond/other cause)

Required ICSU log for further troubleshooting ? • Inter-system Hard Handover

•RL fails

•Other Non-RL Fails •Pre-emption

HSDPA Retainability

•The normal transition from HS-DSCH to FACH/DCH are considered as a normal HS-DSCH release (including transitions due to mobility and pre-emption) HSDPA Drop reasons: RL fails, Non-RL fails, Mobility fails, Pre-emption fails, other fails

(56)

HSDPA Retainability

•The retainability of all successfully allocated E-DCH resources for NRT traffic

(57)

Drop Call Rate (DCR)

Call Drop rate (CDR) is calculated based on RAB activation failures • Call is dropped if one (or more) of the following RAB, RB or RL, drops. 2. Identify DCR top offenders…. few cells?…. Any particular area ? Known Coverage issue? Need a new site ?

(availability should be 100%)---- cell level report

/ sector & same for neighbor cells?--- alarm history especially for transmission issues (NBAP link failures/T1 fluctuations?) (Radio fails)-- Not RF(Iu, Iur, BTS, RNC, MS, CIPH, UE, trans fails)

due to Frozen BTS/BTS not responding

NBAP Signalling Per cause Report

Check Uplink CE Usage(shouls not be >80-85%--- NodeB Utilization/CE Utilization Report)

RNSAP/NBAP Signalling

DSP Resource Usage, DSP State Changes- System reset/user reset & DSP_Service_Statistics reports

Check physical channel reconfiguration failure rate (IFHO, ISHO, code optimisation)

NRT_Radio_Bearer_stats report for Prx & Ptx ratio

is insufficient , rec. 500ms)--- RRC signalling report

RAB_STP_FAIL_XXX_IUB_AAL2, M1001C531-C533, •Use AAL2 Multiplexing in case of two WAM, Iub Capacity report, NRT_Radio_Bearer_stats--AAl2 congestion

check the Site location, Neighbors, Cell to cell HO stats(SHO,IFHO,ISHO), PRACH delay distance and Ec/No quality distribution statistics















1 _____

____

%100_

LinksRadioServerBestofNumber

LinksRadioofNumberTotal

OverheadSHO

(58)

Coverage or interference-- Cell Power Report Missing neighbor checks-- for neighbor optimization

From cell level report

Coverage_Quality_ISHO_Performance_per_Cause reports--- UL DCH qual, UE tx pwr, DL DPCh, RSCP/EcNo, IMSI, Emergency drops, PRx total, PTx Total, drops due to service based HO GSM frequency plan neighbour RNC and MSC database consistency audit( for BCCh/BSIC collision)

If No cell found ratio is>90% & enough ADJIs--- Wrong reference Clock tuning( 10MHz tunning)

TCH Blocking/TCH congestion/TCH failures/2G traffic/2G coverage & Interference

Missing Neighbor chk / best server Ec/No should not be less than -12db

if UE does not receive the RRC Setup Message from RNC./ Antenna tilt(CPICH RSCP should not be<-102dbm) / PRACH_Propagation_Delay Report ( Cell range in TMO Sites-20Kms)

9. HO issue/HO fails? All Neighbor Exists? SHO….ISHO……IFHO…….?? Neighbor Add/delete?

HO success rate per adjacency counters-- delete/create them again,

Audit Adjacent sites for Alarms/capacity/traffic and visualization check with map

If No cell found ratio >40%-- 3G cell at inter-RNC border/ 3G cell covers a coverage hole---- RF & ISHO neighbor optimization Check missing neighbour/badly performing neighbors(ISHO Adjacencies report),

(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















1 _____

____

%100_

LinksRadioServerBestofNumber

LinksRadioofNumberTotal

OverheadSHO

(59)

Packet service RAB active, drops reasons: Packet session, drops reasons: Iu HS-DSCH/E-DCH DR, RL Iur HS-DSCH/DCH DR, RL RNC DCH/DCH DR, RL MS HS-DSCH/E-DCH DR, Other UE HS-DSCH/DCH DR, Other Trans DCH/DCH DR, Other Radio fails

NRT PS RAB active fail due

to---1. Radio-- Chk NRT Radio Bearer fails due to radio--- NRT_DCH_Allocations_Statistics/ NRT_Radio_Bearer_stats/ SHO Overhead NRT_RT chk?/ Active_Set_Size_for_NRT-RT_Traffic report

2. BTS-- chk BTS HW resources-- NRT_Radio_Bearer_stats report for BTS congestion

Failed SCC due to HSDPA return channel-- chk SCC fails-- Service_Session_Retainability report--for HS_DSCH SCC fails HSPA_Serving_Cell_Change report-- for reasons, causes, fails

SCC=Serving Cell Change

3. Iu-- chk core network parameter

settings---4. Iur-- Inter RNC mobility?

5. RNC-- RNC Internal problem

6. UE-- Terminal problem

Release due to RL Failure counters: M1022C57 PS_REL_RL_FAIL_HS_E_INT M1022C58 PS_REL_RL_FAIL_HS_E_BGR M1022C59 PS_REL_RL_FAIL_HS_D_INT M1022C60 PS_REL_RL_FAIL_HS_D_BGR M1022C61 PS_REL_RL_FAIL_D_D_INT M1022C62 PS_REL_RL_FAIL_D_D_BGR

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

Release due to Other Failure counters: M1022C63 PS_REL_OTH_FAIL_HS_E_INT M1022C64 PS_REL_OTH_FAIL_HS_E_BGR M1022C65 PS_REL_OTH_FAIL_HS_D_INT M1022C66 PS_REL_OTH_FAIL_HS_D_BGR M1022C67 PS_REL_OTH_FAIL_D_D_INT M1022C68 PS_REL_OTH_FAIL_D_D_BGR

are incremented in case the PS allocation is released due to any other reason expect normal, pre-emption or RL failure















1 _____

____

%100_

LinksRadioServerBestofNumber

LinksRadioofNumberTotal

OverheadSHO

(60)

1. RL Fails

DL coverage & Interference-- PRACH delay range report/tilt Neighbor Optimization etc.

NRT_Radio_Bearer_stats--AAl2 congestion

RB reconfiguration failure ratio ( If ATO setting is insufficient , rec. 500ms)--- RRC signalling report

Evaluate Cell resource Prx and Ptx (for example high uplink interference)--NRT_Radio_Bearer_stats report for Prx & Ptx ratio

NBAP_Signalling report-- Radio link - SRNC, Radio link - DRNC, RL setups/reconf fails for HSDPA MAC-d flow

Required ICSU log for further troubleshooting ?

•The normal transition from HS-DSCH to FACH/DCH are considered as a normal HS-DSCH release (including transitions due to mobility and pre-emption)

RL fails, Non-RL fails, Mobility fails, Pre-emption fails, other fails Compare RL fails with -- Cell Upd ATT RL Fails & Cell Upd ATT RLC Fails--recoverable error ( present in retainability report)

Check SCC Failure rate--HSPA_Serving_Cell_Change report (HSDPA SCC fails due to UE,BTS,Trans,AC)-- high SCC failures lead to radio link failure Radio fails -- UL coverage(TMA/MHA chk) & Interference

Iub -- HSPA Overview report-- for Iub congestion

RAB_ACC_FAIL_Iub AAl2 fails--- •Check RAB_STP_FAIL_XXX_IUB_AAL2, M1001C531-C533, •Use AAL2 Multiplexing in case of two WAM, Iub Capacity report,

Iub_Traffic_-_FP_layer report-- for rejections, discarded frames & lost PDUs with reasons

CE resource congestion--- CE utilization/Cell capacity/Number_of_HSPA_Users_and_UE_capability(Simultaneous users, NRT DCH select due to too many hsdpa/hsupa users) Check CQI distribution (HSPA Overview report)

EcNo distribution for bad coverage issues- (M1007C38-M1007C47, CPICH EcNo class 0-9)

Check Active_Set_Size_for_NRT-RT_Traffic report-- Active set update fails, 1-2-3 cells (% & no.) in active set for different RT & NRT services Check HSDPA FMCS Mobility Control Parameter --(Add/Drop window, handover or SCC too late, SCC parameter)

Check call re-establishment T315 timer due to radio link failure 9 (60 secs in TMO)

2. Non- RL Fails/Others-- Check

UE responding with some failure msg or not responding to some msg, but no RL failure (timer expiry) Chk RNC fails & use RNC logging If required

Check RB reconfiguration, physical channel reconfiguration, NBAP RL reconfiguration failure rate Release due to RL Failure counters:

M1022C57 PS_REL_RL_FAIL_HS_E_INT M1022C58 PS_REL_RL_FAIL_HS_E_BGR M1022C59 PS_REL_RL_FAIL_HS_D_INT M1022C60 PS_REL_RL_FAIL_HS_D_BGR M1022C61 PS_REL_RL_FAIL_D_D_INT M1022C62 PS_REL_RL_FAIL_D_D_BGR

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

(61)

E-DCH Rel due to RL Failures E-DCH Rel due to other failures

Traffic_on_AAL5 report •The retainability of all successfully allocated E-DCH resources for NRT traffic

RL fails, Non-RL fails, E-DCH RelRate(HS-DSCH SCC), other fails

•There are several reasons for HSUPA release: –RNC_1108a

–RNC_1109a

•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

Cell capacity report -- UL load- HSUPA Physical CH pwr

HSPA serving cell change report -- HSUPA SCC- E-DCH down to DCH, Inter RNC Soft handover performance report -- HSUPA SHO Success Rate

HSPA Overview report -- HSUPA(2ms/10ms TTI thp, E-DCH 2ms TTI utilization), HSUPA Transmitted Power Ratio, HSUPA usage( happy Bit rate, 2ms/10ms TTi trans usage rate, MAC-e PDU not transmitted/not received

correctly/ceived correctly but lost)

(62)

Call Drop rate (CDR) is calculated based on RAB activation failures Call is dropped if one (or more) of the following RAB, RB or RL, drops.

(63)

Coverage or interference-- Cell Power Report Missing neighbor checks-- for neighbor optimization

(64)

1. Radio-- Chk NRT Radio Bearer fails due to radio--- NRT_DCH_Allocations_Statistics/ NRT_Radio_Bearer_stats/ SHO Overhead NRT_RT chk?/

2. BTS-- chk BTS HW resources-- NRT_Radio_Bearer_stats report for BTS congestion

Failed SCC due to HSDPA return channel-- chk SCC fails-- Service_Session_Retainability report--for HS_DSCH SCC fails

(65)

HS-DSCH Allocation release

DL coverage & Interference-- PRACH delay range report/tilt

NRT_Radio_Bearer_stats--AAl2 congestion

RB reconfiguration failure ratio ( If ATO setting is insufficient , rec. 500ms)--- RRC signalling report

Evaluate Cell resource Prx and Ptx (for example high uplink interference)--NRT_Radio_Bearer_stats report for Prx & Ptx ratio

Cell Upd ATT RLC Fails--recoverable error ( present in retainability report)

--HSPA_Serving_Cell_Change report (HSDPA SCC fails due to UE,BTS,Trans,AC)-- high SCC failures lead to radio link failure -- UL coverage(TMA/MHA chk) & Interference

HSPA Overview report-- for Iub congestion

RAB_STP_FAIL_XXX_IUB_AAL2, M1001C531-C533, Use AAL2 Multiplexing in case of two WAM, Iub Capacity report,

rejections, discarded frames & lost PDUs with reasons

CE utilization/Cell capacity/Number_of_HSPA_Users_and_UE_capability(Simultaneous users, NRT DCH select due to too many hsdpa/hsupa users)

for bad coverage issues- (M1007C38-M1007C47, CPICH EcNo class 0-9)

Check Active_Set_Size_for_NRT-RT_Traffic report-- Active set update fails, 1-2-3 cells (% & no.) in active set for different RT & NRT services HSDPA FMCS Mobility Control Parameter --(Add/Drop window, handover or SCC too late, SCC parameter)

due to radio link failure 9 (60 secs in TMO)

UE responding with some failure msg or not responding to some msg, but no RL failure (timer expiry)

RB reconfiguration, physical channel reconfiguration, NBAP RL reconfiguration failure rate Release due to Other Failure counters:

M1022C63 PS_REL_OTH_FAIL_HS_E_INT M1022C64 PS_REL_OTH_FAIL_HS_E_BGR M1022C65 PS_REL_OTH_FAIL_HS_D_INT M1022C66 PS_REL_OTH_FAIL_HS_D_BGR M1022C67 PS_REL_OTH_FAIL_D_D_INT M1022C68 PS_REL_OTH_FAIL_D_D_BGR

(66)

E-DCH Allocation release

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

-- UL load- HSUPA Physical CH pwr

-- HSUPA SCC- E-DCH down to DCH, Inter RNC -- HSUPA SHO Success Rate

HSPA Overview report -- HSUPA(2ms/10ms TTI thp, E-DCH 2ms TTI utilization), HSUPA Transmitted Power Ratio, HSUPA usage( happy Bit rate, 2ms/10ms TTi trans usage rate, MAC-e PDU not transmitted/not received

(67)

(68)

(69)

(70)

high SCC failures lead to radio link failure

(71)

(72)

SHO success rate

SHO Reports:

Soft_Handover_Performance Cell level

SHO_Adjacencies Cell level

Yes-- (check Iur capacity and SRNC relocation problem)

No-- SC clash?---yes(fix SC clash)

•SHO success rate KPI (RNC_195a) is informing how many successful Active set updates we will have, compared to initial Addition/Replacement/Deletion requests.

AS update RT+NRT, RT Update % - 1a,1b,1c, NRT Update % - 1a,1b,1c, Events Ratio RT+NRT, HSUPA SHO Success Rate, CPICH EcNo Report(in % & no.) - Excellent, good, Acceptable, Poor, Bad SHO adjacencies are checked to increase SHO Success Rate, Target cells without neighbors are checked with their attempts & SR, Also their Avg. EcNo & RSCP shown their,

then decide whether neighbor is to be added or not.---- ADJs addition & deletion of neighbors with no share

Check SHO KPI if performance < 90% ( leads to Radio failure)--- Yes –Check if cells are at RNC border

–Detect badly performing neighbours using HO success rate per adjacency counters-- delete/create them again, check SHO Overhead

–High incoming HO failure rate in all ADJS – check sync alarms

–Audit Adjacent sites for Alarms/capacity/traffic and visualization check with map –Evaluate HO control parameters and trigger threshold

Check if DL Active set update received(Active_Set_Size_for_NRT-RT_Traffic Report)

no --- congestion on target cell ( Load optimization)

DL Tx power max.?---yes ( in this case; Link is unbalanced--- do CPICH Optimization Yes-- UE Tx Power max.?--- no(chk RF levels)

yes( check Uplink interference? )

RNC_153b SHO SR, RT

RNC_192b SHO SR, NRT

REASONOTHERSTARTEDSCCUPDSETACTIVESTARTEDSCC

ERRORSIRULSTARTEDSCCECNOCPICHSTARTEDSCC

SUCCESSFULBTSINTERSCCSUCCESSFULBTSINTRASCC

ARNC

_______

______

100%733_







(73)

If UL interference----load optimization/External Interferer

SHO based on DSR( Detected Set relation)-- Enabled in TMO

Example: SHO Parameters Changed

ISHO Success Rate

•Replacement parameters were changed in live network in the RU10 pilot: –FMCS: ReplacementWindow 2dB -> 6dB

–FMCS: ReplacementTime 100ms -> 640ms •Addition and drop parameters were:

–FMCS: AdditionWindow = 4 dB –FMCS: AdditionTime = 100 ms –FMCS: DropWindow = 6 dB –FMCS: DropTime = 640 ms •Periodical reporting intervals

–AdditionReportingInterval = ReplacementReportingInterval = 0.5s –DropReportingInterval = disabled (now event based as in RAS06)

SHO Update Attempt RT Same, SHO success ratio RT increased from 99.8 to 99.9% and above.

RAB Attempts CS Voice same, RAB Success ratio CS Voice increased from 99.4 to 99.6%.

REASONOTHERSTARTEDSCCUPDSETACTIVESTARTEDSCC

ERRORSIRULSTARTEDSCCECNOCPICHSTARTEDSCC

SUCCESSFULBTSINTERSCCSUCCESSFULBTSINTRASCC

ARNC

_______

______

100%733_







(74)

The inter-system handover measurement is carried out in the serving RNC (SRNC)

The RT and NRT Inter System HO differs in nature. Therefore the ISHO KPI can be spitted in RT and NRT parts •ISHO success rate for RT services (RNC_300g)

•ISHO success rate for NRT services (RNC_301e)

REASONOTHERSTARTEDSCCUPDSETACTIVESTARTEDSCC

ERRORSIRULSTARTEDSCCECNOCPICHSTARTEDSCC

SUCCESSFULBTSINTERSCCSUCCESSFULBTSINTRASCC

ARNC

_______

______

100%733_







(75)

If RRC connection drops during ISHO… TRelocOverall timer expires[8sec](in case of RT); RRCtmriRCCl timer expires[8sec](in case of NRT); cause can be: CPICH RSCP, CPICH EcNo, UL-DCH, TxPwr, DL-DPCH

If No cell found ratio is>90% & enough ADJGs--- Wrong reference Clock tuning( 10MHz tunning)

TCH Blocking/TCH congestion/TCH failures/2G traffic/2G coverage & Interference

ISHO Cancellation

Parameters:

Steps to Improve ISHO SR:

2. ISHO parameter threshold changes

If No cell found ratio >40%-- 3G cell at inter-RNC border/ 3G cell covers a coverage hole---- RF & ISHO neighbor optimization If No cell found ratio<40% & ISHO Success rate<90%--- Investigate 2G

•The inter-system measurement phase takes a few seconds and during that time the conditions in the WCDMA layer may change => Cancellation –Event 1E cancellation

–AS Update (1A or 1C) can also cancel ISHO in case of RSCP or Ec/No triggered ISHO

§If the CPICH Ec/No or the CPICH RSCP of this cell is found to be greater than or equal to the threshold for event 1E •No cancellation once measurement phase is completed

•Activation per RNC required with parameter RNC: ISHOCancellation

•Enabled per trigger reasons with parameters FMCG: ISHOClcauseXXX

•Parameter FMCG: DLDPCHTxPwrClOffset allows to influence cancellation (-3 in TMO)

•RNC: MaxNumISHOClPerAS sets the maximum number of ISHO cancellations per UE and per active set

1. Multiple BSIC Identification feature enabled chk?-- BSIC Identification of max. 3 GSM carriers simultaneously MultipleBSICIdent parameter---must be set to 'on'

MaxBSICIdentTime is 3 or 4 seconds if the overall procedure of HandOver to GSM is close to typical value of 10 sec (GsmMeasRepInterval * GsmMaxMeasPeriod); visible benefit in reducing CM.

REASONOTHERSTARTEDSCCUPDSETACTIVESTARTEDSCC

ERRORSIRULSTARTEDSCCECNOCPICHSTARTEDSCC

SUCCESSFULBTSINTERSCCSUCCESSFULBTSINTRASCC

ARNC

_______

______

100%733_







(76)

3. Force Decode BSIC feature for NRT--> •ISHO success rate improved a lot -> ISHO cell found ratio decrease 4. Missing ADJG/bad performing neighbors(SR/Adjacency)-- ISHO Adjacencies report---> to be defined & corrected 5. Compressed mode parameter set changes

6. GSM Measurement reporting parameters changes

a) AdjgTxPwrMaxTCH-- Maximum UE TX Power on TCH(HCConfiguratio

b) AdjgRxLevMinHO (n)--- minimum required GSM RSSI level

--->

ISHO Parameters

(XX=AMR,CS,NrtPS,RtPS)

Multiple BSIC identification – RU20

7. Changes in Decision Algorithm parameters

c) GsmMeasAveWindow --

kitni measurement report se RNC avg GSM RSSI value for handover nikallegi---- 1...32 MeasRep, step 1 MeasRep,

1. Triggering

2. GSM measuring

3. Decision

3. Decision Algorithm

AdjgTxPwrMaxTCH

AdjgRxLevMinHO (n)

GsmMeasAveWindow

UE Tx Power (Event 6A) Threshold:

GsmUETxPwrThrXX

L3 filter: GsmUETxPwrFilterCoeff Hysteresis margin:

GsmUETxPwrTimeHyst Data rate threshold HHOMAxAllowedBitrateUL

DL DPCH power Threshold:

GsmDLTxPwrThrXX Data rate threshold HHOMAxAllowedBitrateDL CPICH RSCP (Event 1F) Thresholds: HHoRscpThreshold HHoRscpCancel L3 filter: HHoRscpFilterCoefficient Timers: HHoRscpTimeHysteresis HHoRscpCancelTime

Handover Execution

GsmMeasRepInterval GsmNcellSearchPeriod GsmMinMeasInterval GsmMaxMeasPeriod 2. GSM measurement reporting

REASONOTHERSTARTEDSCCUPDSETACTIVESTARTEDSCC

ERRORSIRULSTARTEDSCCECNOCPICHSTARTEDSCC

SUCCESSFULBTSINTERSCCSUCCESSFULBTSINTRASCC

ARNC

_______

______

100%733_







(77)

ISHO Failure Scenarios

CM start not possible

•The RNC initiates BSIC identification to the UE for max three GSM carriers simultaneously.

•If the ISHO attempt to the best neighbour cell fails, a new attempt to the other cell can be started without new inter-system measurements in compressed mode. –Reduces compressed mode measurements

–Increase ISHO success rate

•ISHO may fail if the initial BSIC identification of the best GSM cell (according to the GSM RSSI measurements) fails, or the target GSM cell is fully loaded. •Instead of waiting the penalty period and then retrying the HO with new CM measurements, the BSIC identification for more than one GSM cell is performed.

•This increases the probability of successful BSIC identification and allows another handover attempt to the second or third best cell without repetitive GSM measurements if the first handover attempt fails.

REASONOTHERSTARTEDSCCUPDSETACTIVESTARTEDSCC

ERRORSIRULSTARTEDSCCECNOCPICHSTARTEDSCC

SUCCESSFULBTSINTERSCCSUCCESSFULBTSINTRASCC

ARNC

_______

______

100%733_







(78)

HS-DSCH Serving Cell Change

There seems not to be a relation with poor SCC success and HSDPA retainability.

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

REASONOTHERSTARTEDSCCUPDSETACTIVESTARTEDSCC

ERRORSIRULSTARTEDSCCECNOCPICHSTARTEDSCC

SUCCESSFULBTSINTERSCCSUCCESSFULBTSINTRASCC

ARNC

_______

______

100%733_







(79)

(80)

From cell level report

SHO success rate KPI (RNC_195a) is informing how many successful Active set updates we will have, compared to initial Addition/Replacement/Deletion requests.

RT Update % - 1a,1b,1c, NRT Update % - 1a,1b,1c, Events Ratio RT+NRT, HSUPA SHO Success Rate, CPICH EcNo Report(in % & no.) - Excellent, good, Acceptable, Poor, Bad SHO adjacencies are checked to increase SHO Success Rate, Target cells without neighbors are checked with their attempts & SR, Also their Avg. EcNo & RSCP shown their,

then decide whether neighbor is to be added or not.---- ADJs addition & deletion of neighbors with no share

HO success rate per adjacency counters-- delete/create them again,

Audit Adjacent sites for Alarms/capacity/traffic and visualization check with map