Professional Documents
Culture Documents
UE measurements are different than to RF scanner measurements. The Scanner measures all SCs, whereas the UE only
measures SC signals from the cells that the system has informed/ordered the UE through the BCH (neighbour list) or via the
“measurement control” message.
With this we can get following info:
The BLER downlink
Carrier RSSI
Data Throughput Downlink
Data Throughput Uplink
Ec/No Active Cell
Ec/No Monitored Cell
Pilot BER
Random Access Initial Tx Power
Random Access Preamble Count
Random Access Preamble Step
Random Access Tx Power
SIR target
UE Tx Power
Call Statistic: AMR, CS and PS data calls
Supported Measurements Layer 1 handset measurements (for example EcNo, TxPow, etc.)
with Handset are: RRC Layer 3 signalling – Call Control (CC), Mobility Management (MM), GPRS Mobility Management,
GPRS Session Management
Missing Site- No
dominance
server in the
area
Planned Site
282
280 281
Note !!
Soc Classification level
9 © Nokia Siemens Networks Presentation / Author / Date
Verification of Swapped feeder or other issue
No measurements
SC161 and SC162 Tx in vicinity of sector
C (SC = 162)
from same sector
crossed feeders can occur at:
• Antenna
• Input to BTS SC162
Sector B-SC161 Sector C-SC162
• Within the BTS
Soc Classification level
10 © Nokia Siemens Networks Presentation / Author / Date
RSCP Verification
Check that the RSCP levels for the area meet the target thresholds for the
service and environment (clutter, building loss)
If coverage is acceptable then check for area of poor EcNo in the area.
Pilot pollution areas can be shown with Scanner Pilot Pollution query with
user defined RSCP and EcNo levels
(CPICH_SCAN_EcNo_Sorted_By_EcNo (0)<-12)
AND (CPICH_SCAN_RSCP_Sorted_By_EcNo
(0)>-92)
Pilot polluter workbook shows the worst polluters in the area e.g. SC 344
have most of the samples
SC 344 displayed
over pilot pollution
Scanner sees 5
SC’s, all within 5 dB
of each other.
This is clearly an
area suffering from
pilot pollution.
SC 272 is the furthest away these sites and is joint second best server.
SC 272
By using UE together with Scanner during testing we can check the UEs
transmit power for problem areas where UE cannot maintain the link quality
• Check if the cause of call setup failure is CPICH RSCP and Ec/No
coverage problem
• The received best server’s CPICH RSCP and Ec/No will be compared to
the coverage thresholds at the location where call setup failed and if best
server’s CPICH RSCP OR Ec/No is less than the thresholds, coverage
optimisation will be performed.
• The thresholds of CPICH RSCP and Ec/No depend on UE’s sensitivity:
– CPICH RSCP coverage threshold = -110 dBm
– CPICH Ec/No coverage threshold = -16 dB
3.70%
8.33% 22.22% RF Issue : Interference
8.33%
29.63%
8.33%
AS Update Failure :
RF Issue : Interference
Cause unknown
UE Issue UE Issue
Mechanical
Down tilt kit
Deformation of the
horizontal pattern
Manual Remote
use use
Horizontal pattern
remains constant
Impact
Impacton
onEc/No
Ec/No
Site JS9125 (SC28) from cluster Site JS9125 (SC28) was tilted by 1
Soc Classification level5 is overshooting to cluster 1 deg (E-tilt From 4 deg to 5 deg)
29 © Nokia Siemens Networks Presentation / Author / Date
Neighbour List Verification
Inter- Inter-
Frequency System Total max 111 in RNC
Neighbors Neighbors database, limitation due to
Cell r specifications of SIB11/12
(32 /carrier)
Cell k
size
Max. 32
Max. 48
Cell l Cell s
Cell m Cell t
Cell n Cell u
Cell o Cell v
Each neighbour has a set of associated parameters e.g. CPICH measurement offset
The post processing tool should be able to suggest appropriate neighbour lists
Strategy for initial system deployment is to place the emphasis upon adding
neighbours rather than removing them
Soc Classification level
30 © Nokia Siemens Networks Presentation / Author / Date
Max. 96
Neighbour List Verification – SIB 11/12 neighbours due
SIB limitation
When offsets are added to the neighbours or the CPICH power of the neighbour cell
is different to that of the serving cell the length of the message for each neighbour in
SIB 11/12 is increased
• The length of one ADJS with no offsets is 48 bits
• The length of an ADJS with AdjsQoffset1 or AdjsQoffset2 is 48 or 56 bits on a
case by case basis (average length 55.2 bits)
• The length of an ADJS with AdjsQoffset1 and AdjsQoffset2 is 56 or 64 bits on a
case by case basis (average length 62.1 bits)
When the neighbour cell has a different CPICH Tx Power from the serving cell
• Without Offset and AdjsPtxCPICH : 54.2bits
• With AdjsQOffset1 or AdjsQOffset2 : 61.1bits
• With both AdjsQOffset1 and AdjsQOffset2 : 68bits
There are a number of approaches that can be used to both plan and verify
the neighbour plan
Neighbour Neighbour
Creation Verification
Neighbour
Manual Check Analytical
Creation
Planning Tool
Other
Manual Check
Drive Testing
Measured
Network Stats
• 6 missing neighbours
were identified for this
site and added – Manual
Check would have
identified at least 5
Time
SC Site Sector Num Of Samples Suggested NBR Additions
216 Ewer Park Stud 00161126C 97 85 (47.4%); 303 (17.5%)
349 Reading Rubgy FC 00179719B2 97 351 (28.9%)
83 WOODLEY ATE 00001085A 96 350 (34.4%); 84 (25.0%)
436 TILEHURST ATE 00001081B 90 434 (22.2%); 283 (22.2%)
Numerical Analysis
Soc Classification level
37 © Nokia Siemens Networks Presentation / Author / Date
Neighbour List Verification
Try to figure the possible area/direction of the
Call set-up Failure interference by checking PrxTotal level on
neighbouring cells.
Call drop
The PrxTotal level is significantly
High PrxTotal due to UL Alternatively use spectrum analyser & directive
higher than expected in no/low load
External interference antenna to locate interferer. Inform
conditions.
operator/regulator about the found conditions.
Check if auto-tuning range is large enough (20
dB).
Success
Setup Access Complete dropped, also active RAB is
dropped.
Complete Complete
Active RAB setup
Access
Attempts to start the call
Release
RAB setup access
Active
RRC RAB active phase
Attempts
Fail_MAC_d_setu
RRC_setup/SRB_act p_HSDPA
fails, RB_setup failures
for HSDPA
Top (N) RRC Setup Top (N) RAB Setup/Access
and Access failures or PS Setup failures
Setup
Cell and Neighbour Failure
Cells availability Sites Cause? setup Setup
/Access
Alarms/Tickets OK ? RNC Troubleshooting
Yes BTS/TRANS/FROZBS Setup/Access
AC UL/DL
Setup setup Interference
(DL codes)
/Access
DCH reconfiguration
Capacity
failures AC/BTS/trans Optimisation
RAB/DCH setup
SHO branch setup fail Access &failures, UL
BTS/Iub, RNC capacity Rej_DCH_due to coverage counters to
SW, new DSP counters power or codes see UL spikes
SRNS
(UL/DL) Yes 3G cell at
inter-RNC
Relocation/Iur border ?
RAB setup fail voice troubleshooting
Iur/trans, DCH setup NO
failure for NRT in Iur
Interference
RF Coverage/Int
SHO based on DSR,
CPICH EcNo Optimisation erference
difference Coverage
Soc Classification level
51 © Nokia Siemens Networks
Low CSSR
• RRC Setup Analysis
1. Check the problem cells and its neighbouring cells of any faulty alarms
2. Identify root cause failure distribution using Service Report -> RSRAN073
3. RRC_CONN_STP_FAIL_AC
Check UL Interference, DL Power & Code occupancy if there is need to upgrade radio capacity
UL Power Spikes -> Disable UL Admission Control to if the number of failures is critical (Prxtarget ->30 dB)
M1002C1 CH_REQ_LINK_REJ_UL_SRNC ----> Evaluate Prx Resource Problem
M1002C2 CH_REQ_LINK_REJ_DL_SRNC ----->Evaluate Ptx Resource Problem
4. RRC_CONN_STP_FAIL_BTS
Evaluate NBAP counters (radio link reconf. Failures) and KPIs for troubleshooting BTS resources
Check BTS configuration in terms of WAM and CE allocation – Use Channel Element (5001) Counters in order to
evaluate lack of Channel Elements (more info in RSRAN066)
Expand the Capacity or decrease the traffic offered to the site
In case BTS is not responding delete and re-create COCO
5. RRC_CONN_STP_FAIL_TRANS
Evaluate Number of reconfiguration failure due the transmission
Check COCO Configuration
Use AAL2 Mux in case of two WAM
Expand the Iub capacity or decrease the traffic offered to the site
6. RRC_CONN_STP_FAIL_RNC
Typically RNC fault or Incoming SRNC Relocation Failure (inter-RNC border)
Required ICSU log tracing if no RNC fault or SRNC relocation problem
Soc Classification level
52 © Nokia Siemens Networks
Low CSSR Service Level -> RSRAN073
X
RRC: RRC Connection Setup
balance UL and DL Complete (DCH) NBAP: Synchronisation Indication
(if UL interference if
not the cause) UE BT
S
X RN
C
RRC Access Failures for L1 synchronization
UE BT
S
X RN
C
500000 100.00%
400000 80.00%
average
300000 60.00%
CDF
200000 40.00%
100000 20.00%
0 0.00%
1 200.00
Temporary High UL M1000C334 Cell_Resource RTWP_CLASS_14
interference: M1000C335 Cell_Resource RTWP_CLASS_15
class_21 could be M1000C336 Cell_Resource RTWP_CLASS_16
1 000.00
seen M1000C337 Cell_Resource RTWP_CLASS_17
800.00
M1000C338 Cell_Resource RTWP_CLASS_18
M1000C339 Cell_Resource RTWP_CLASS_19
600.00
M1000C340 Cell_Resource RTWP_CLASS_20
M1000C341 Cell_Resource RTWP_CLASS_21
400.00
200.00
0.00
With RU10, there is new counters to measure the setup success of standalone Signaling Radio
Bearers (SRBs). Standalone SRB means a successfully established RRC connection that is
waiting for the RAB assignment
SRB active fail is pegged when RNC sent RRC:RRC connection Release before RAB assignment
With RNC_1219a, this give better visibilities where low CSSR is somehow caused by failure in
active standalone SRB phase
1. Check the problem cells and its neighbouring cells of any faulty alarms
2. Identify root cause failure distribution and main failure contributor using Services -> RSRAN073
3. RAB_STP_FAIL_XXX_AC
Check UL Interference, DL Power & Code occupancy if there is need to upgrade radio capacity
REQ_CS_VOICE_REJ_UL_SRNC -> Evaluate Prx cell resource
REQ_CS_VOICE_REJ_DL_SRNC -> Evaluate Ptx cell resource
NO_CODES_AVAILABLE_SF128/SF32 -> Evaluate AMR voice / PS64 code congestion
Check parameter setting with UL throughput based AC and power based AC
4. RAB_STP_FAIL_XXX_BTS
Evaluate NBAP counters (radio link reconf. Add failures) and KPIs for troubleshooting BTS resources
Check BTS configuration in terms of WAM and CE allocation – Use Channel Element (5001) Counters in order to evaluate lack of
Channel Elements
Expand the Capacity or decrease the traffic offered to the site
5. RAB_STP_FAIL_XXX_TRANS
Evaluate Number of reconfiguration failure due the transmission
Check M1005C128 CANC_ADD_SRNC_TRAN_STP_FAIL
Check RAB_STP_FAIL_XXX_IUB_AAL2, M1001C531-C533
6. RAB_ACC_FAIL_XXX_UE
Evaluate Cell resource Prx and Ptx (for example high uplink interference)
Check RB reconfiguration failure ration ( If offset for activation time (RNC) setting is insufficient – recommmended is 500-700ms )
7. RAB_ACC_FAIL_XXX_RNC
Typically RNC fault or Incoming SRNC Relocation Failure (inter-RNC border)
Required ICSU log tracing if no RNC fault or SRNC relocation problem
9. RAB_Setup_FAIL_CS_Voice_Iur_TR
Counter incremented when a CS voice traffic class RAB setup fails due to Iur transport resources shortage
10. RAB_Setup_FAIL_CS_Voice_Iu_CS
Counter incremented when a CS voice traffic class RAB setup fails due to Iu-CS transport resources
Since RNC_576c (M1001) is measured NRT DCH setup upto 0/0kbps, it is always showing
>99.5%. So it is not useful for data call setup analysis
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)
M1001 M1022
60.00
M1002C626 Traffic REJ_DCH_DUE_POWER_INT_UL
50.00 150.00 M1002C627 Traffic REJ_DCH_DUE_POWER_BGR_UL
M1002C628 Traffic REJ_DCH_REC_DUE_PWR_INT_UL
40.00
Reconfig M1002C629 Traffic REJ_DCH_REC_DUE_PWR_BGR_UL
30.00 reject due to 100.00
Cannot differentiate
Evaluate Dominant failures: Rel99 DCH , HSDPA,
HSUPA setup failure
Configuration & NO
SHO YES
SHO Success Rate Relocation
< 90%?
success in target
NO
New site ? RNC
ISHO ISHO NO Analyse last detailed RF and IFHO neighbour
Failures radio measurements optimisation
• 4. Check ISHO KPI if RT ISHO < 90% or NRT < 80% (leads to radio failure)
• Check missing neighbour (M1015), GSM frequency plan neighbour 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
• 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)
M1007C71SETUP_FAIL_SHO_BRANCH_BTS : When the SHO branch setup fails due to BTS resources.
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. The counter is updated for the cell
where the failure occurred.
M1007C72 SETUP_FAIL_SHO_BRANCH_IUB :. When the SHO branch setup fails due to Iub transport. The
transport failures include both CAC (Connection Admission Control) negative acknowledgements and
signaling failures.
RU10 also brings new counters to identify Ecno difference between source – target
cell pairs and average Ecno, average RSCP for the neighbour cells based on
scrambling codes
Counters updated if RAN1191 Detected Set Reporting and Measurements and
M1013C2 RAN1189
AutoDef_SHO_v2CPICH Ec/N0 Difference Counters per Cell Pair feature is licensed
M1028C0 Autodef_SHO_DSR CPICH_ECNO_DET_SUM
CPICH_ECNO_SHO_DIFF_SUM
M1013C3 AutoDef_SHO_v2 CPICH_ECNO_SHO_DIFF_DENOM
M1028C1 Autodef_SHO_DSR CPICH_ECNO_DET_DENOM
M1028C2 Autodef_SHO_DSR CPICH_RSCP_DET_SUM
M1013C4 AutoDef_SHO_v2 CPICH_ECNO_SHO_SUM M1028C3 Autodef_SHO_DSR CPICH_RSCP_DET_DENOM
M1013C5 AutoDef_SHO_v2 CPICH_ECNO_SHO_DENOM
M1013C6 AutoDef_SHO_v2 CPICH_RSCP_SHO_SUM
M1013C7 AutoDef_SHO_v2 CPICH_RSCP_SHO_DENOM
KPI Rel99 NRT DCH Drop Call Rate from Packet Call
(M1022)
R99 Dropped Call Ratio from End User Perspective [%]
M1022C61 PS_REL_RL_FAIL_D_D_I NT M1022C62 PS_REL_RL_FAIL_D_D_B GR
M1022C67 PS_REL_OTH_FAIL_D_D_ INT M1022C68 PS_REL_OTH_FAIL_D_D_ BGR
M1022C61 PS_REL_RL_FAIL_D_D_I NT M1022C62 PS_REL_RL_FAIL_D_D_B GR
M1022C67 PS_REL_OTH_FAIL_D_D_ INT M1022C68 PS_REL_OTH_FAIL_D_D_ BGR
M1022C49 PS_REL_NORM_D_D_INT M1022C50 PS_REL_NORM_D_D_BGR
M1022C61 PS_REL_RL_ FAIL_D_D_I NT M1022C62 PS_REL_RL_ FAIL_D_D_B GR
M1022C67 PS_REL_OTH _FAIL_D_D_ INT M1022C68 PS_REL_OTH _FAIL_D_D_ BGR
1
M1022C61 PS_REL_RL_ FAIL_D_D_I NT M1022C62 PS_REL_RL_ FAIL_D_D_B GR
M1022C67 PS_REL_OTH _FAIL_D_D_ INT M1022C68 PS_REL_OTH _FAIL_D_D_ BGR
M1022C49 PS_REL_NOR M_D_D_INT M1022C50 PS_REL_NOR M_D_D_BGR
No
HSDPA Setup Fail Yes Check RNC Unit load (DMPG), max number
RNC Internal of users/RNC, DSP failures and faulty alarms
RSRAN07
Low HSPA Setup Problem In
3
Performance
(RNC_914b) PS Setup Failure Yes
Air Interface
due AC
No
PS Setup Failure
Yes
due BTS
BTS If not DMCU faulty,
check DSP resource
No usage and
availability with
PS Setup Failure
Yes RU10 M609 DSP
Iub
due Iub Service Stats and
Others failure M615 DSP Resource.
No
could be max
HSPA users PS Setup Failure due
Yes
RNC
been reached to, DMCU
or “radio link No
failure” PS Setup failure due to Yes High Traffic
during setup Others Event
Yes
No action needed
Soc Classification level
71 © Nokia Siemens Networks
Low HSDPA Accessibility
With RU10, there is new counters in packet call to identify packet call attempt to cells which
are not HSPA enabled. New KPI (RNC_914b) gives better results in terms of HSDPA
accessibility when networks mixed with HSPA and non-HSPA enabled cells. This avoids
separate aggregation which required previously in RAS06.
RNC_914b does not include statistics from serving cell change mobility. Thus, the
performance could be lower as well due to statistical calculation
400 10
200 5
0 0
1 14 27 40 53 66 79 92 105 118 131 144 157 170 183 196 209 222 235 248 261 274 287
RNC_920a/609a< No No Action
X% Needed
Yes
Yes
HSPA packet call Check SCC Failure Rate – Radio, Iub, CE resource
Radiolink failures congestion
No
Yes
HSPA packet call Check for RNC failures and use RNC logging if
failures - other required
KPI RNC_920a :
• 100 -100 *
sum ( PS_REL_RL_FAIL_HS_E_INT
+ PS_REL_RL_FAIL_HS_E_BGR • RNC_609a:
+ PS_REL_RL_FAIL_HS_D_INT • 100 * sum(REL_ALLO_NORM_HS_DSCH_INT
+ PS_REL_RL_FAIL_HS_D_BGR + REL_ALLO_NORM_HS_DSCH_BGR)
+ PS_REL_OTH_FAIL_HS_E_INT ----------------------------------------------------------------
+ PS_REL_OTH_FAIL_HS_E_BGR
+ PS_REL_OTH_FAIL_HS_D_INT sum( REL_ALLO_NORM_HS_DSCH_INT
+ PS_REL_OTH_FAIL_HS_D_BGR ) + REL_ALLO_NORM_HS_DSCH_BGR
+ REL_ALLO_OTH_FAIL_HSDSCH_INT
-------------------------------------------- + REL_ALLO_OTH_FAIL_HSDSCH_BGR
sum ( PS_REL_RL_FAIL_HS_E_INT + REL_ALLO_RL_FAIL_HS_DSCH_INT
+ PS_REL_RL_FAIL_HS_E_BGR + REL_ALLO_RL_FAIL_HS_DSCH_BGR)
+ PS_REL_RL_FAIL_HS_D_INT
+ PS_REL_RL_FAIL_HS_D_BGR
+ PS_REL_OTH_FAIL_HS_E_INT
+ PS_REL_OTH_FAIL_HS_E_BGR
+ PS_REL_OTH_FAIL_HS_D_INT
+ PS_REL_OTH_FAIL_HS_D_BGR
+ PS_REL_NORM_HS_E_INT
+ PS_REL_NORM_HS_E_BGR
+ PS_REL_NORM_HS_D_INT
+ PS_REL_NORM_HS_D_BGR )
Normal
• release
No No action
RNC_733a < X needed
%
Top N cellsYes
No No No No No
SCC Fail SCC Fail SCC Fail
SCC Fail BTS SCC Fail AC Transmissio SCC Fail UE Others Prevention
n timer
1. Determine HSDPA SCC success ratio (RNC_733a), 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
3. 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)
• Check target cells M1002C521 or M1002C522 or M1000C144 (RAS06) – only when HSDPA static
allocation
• Check target cells number of simultaneous active HSDPA users
Soc Classification level
80 © Nokia Siemens Networks
Low HSDPA SCC Success Ratio
Mobility & Handover –RSRAN033
• 4. If high SCC_FAILED_due_to_BTS
• Check target cells M1002C416/424 SETUP_FAIL_BTS_HS_DSCH_XXX
• Check target cells CE resource utilisation at BH using M5001 counters for lack of UL return
channel resource
• Check NBAP Radio Link Reconfiguration Failure rate
• Check SHO overhead – use lower value for AdditionWindow (closer to 0 dB) in HSDPA FMCS
than in the RT/NRT FMCS, to have smaller SHO area for HSDPA users.
• 5. 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
6. 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
7. If high SCC_FAILED_due_to_Others
• Check RNC internal transport resources usage (DMPG)
• Require ICSU troubleshooting
RECEIVED_HS_MACD_BITS - DISCARDED_HS_MACD_BITS 500
HSDPA_BUFF_WITH_DATA_PER_TTI 2
End user experience v3.0
RECEIVED_HS_MACD_BIT S - DISCARDED_HS_MACD_BITS 500
(HSDPA_USE RS_0_1_IN_CELLS HSDPA_USER S_1_0_IN_CELLS)
2 (HSDPA_USE RS_0_2_IN_CELLS HSDPA_USER S_1_1_IN_CELLS HSDPA_USER S_2_0_IN_CELLS)
3 (HSDPA_USE RS_1_2_IN_CELLS HSDPA_USER S_2_1_IN_CELLS
HSDPA_USER S_0_3_IN_CELLS HSDPA_USER S_3_0_IN_CELLS)
HSDPA_BUFF_WITH_DATA _PER_TTI
HSDPA_USER S_0_1_IN_CELLS HSDPA_USER S_1_0_IN_CELLS HSDPA_USER S_0_2_IN_CELLS
HSDPA_USER S_1_1_IN_CELLS HSDPA_USER S_2_0_IN_CELLS HSDPA_USER S_0_3_IN_CELLS
HSDPA_USER S_1_2_IN_CELLS HSDPA_USER S_2_1_IN_CELLS HSDPA_USER S_3_0_IN_CELLS
Soc Classification level
83 © Nokia Siemens Networks
Low HSDPA Cell/User Throughput
• Below is comparison of all the throughput per user formulas as
well as RNC_722b
Average HSDPA
Throughput per
User has increased
a lot based on
users in data
buffer
6. DMPG resource sharing causes the total throughput per user is not only limited by the #
simultaneous users per cell and their activity but also the amount of simultaneous users per
DMPG (per RNC sharing the total RNC throughput) and their activity
Max HSDPA Throughput per RNC (62 x 7.2Mbps currently on RNC Throughput
450Mbps)
Sum ( #_users_with_data_in_buff_per_TTI / all_active_TTIs) x avg_#_HSDPA_users_in_RNC
HSDPA_NRTD_PEAK_CALLS
Yes
Yes
HSUPA Setup Fail
Check BH Channel element resource usage UL/DL
BTS
Se No
tu HSUPA Setup Fail
Yes Check RB reconfiguration failure rate
p UE (Terminal problem)
fai No
lu
Yes
re HSUPA Setup Fail Check AAL2 connections (not enough CID) or
s TRANS Signalling problems
No
Yes
HSUPA Setup Fail Go for troubleshooting
Other
( E.g. RNC internal failures)
• RNC_915c : • RNC_913a:
• 100 *
• 100* sum(HS_E_REQ_HS_E_ALLO_STRE + sum ( ALLO_SUCCESS_EDCH_INT
HS_E_REQ_HS_E_ALLO_INT + + ALLO_SUCCESS_EDCH_BGR )
HS_E_REQ_HS_E_ALLO_BGR) / sum(
PS_ATT_HSDSCH_EDCH_STRE + ---------------------------------------------
PS_ATT_HSDSCH_EDCH_INT + sum ( ALLO_SUCCESS_EDCH_INT
PS_ATT_HSDSCH_EDCH_BGR - + ALLO_SUCCESS_EDCH_BGR
HS_E_REQ_HS_D_ALLO_STR_CELL - The number of
HS_E_REQ_HS_D_ALLO_BGR_CELL - DCH/DCH allocations + EDCH_ALLO_CANC_NA_AS_BGR
HS_E_REQ_HS_D_ALLO_INT_CELL - after an HS-DCSH/E- + EDCH_ALLO_CANC_NA_AS_INT
HS_E_REQ_D_D_ALLO_STR_CELL - DCH request for the + UL_DCH_SEL_MAX_HSUPA_USR_BGR
HS_E_REQ_D_D_ALLO_BGR_CELL - backg/interactive
traffic class due to the
HS_E_REQ_D_D_ALLO_INT_CELL) cell not supporting + UL_DCH_SEL_MAX_HSUPA_USR_INT
HSUPA and HSDPA
+ UL_DCH_SEL_BTS_HW_INT
+ UL_DCH_SEL_BTS_HW_BGR
+ SETUP_FAIL_EDCH_BTS_BGR
With RU10, there is new counters in packet call to identify + SETUP_FAIL_EDCH_BTS_INT
packet call attempt to cells which are not HSPA enabled. + SETUP_FAIL_EDCH_OTHER_BGR
New KPI (RNC_915c) gives better results in terms of + SETUP_FAIL_EDCH_OTHER_INT
HSUPA accessibility when networks mixed with HSPA + SETUP_FAIL_EDCH_TRANS_BGR
and non-HSPA enabled cells. This avoids separate
aggregation which required previously in RAS06.
+ SETUP_FAIL_EDCH_TRANS_INT
+ SETUP_FAIL_EDCH_UE_BGR
RNC_914b does not include statistics from serving cell
change mobility. Thus, the performance could be lower
+ SETUP_FAIL_EDCH_UE_INT )
as well due to statistical calculation
RNC_919a / No No Action
921b < Needed
X%
Yes
Yes
HSPA packet call Check SCC Failure Rate – Radio, Iub, CE resource
Radiolink failures congestion
No
Yes
HSPA packet call
Check for RNC failures??
failures - other
• RNC_918b:
100 *
sum ( EDCH_SCC_INTRA_BTS_SUCCESS
+ EDCH_SCC_INTER_BTS_SUCCESS )
-------------------------------------------
sum ( EDCH_SCC_STARTED )
Check Mininum, Maximum & Average HSUPA throughput from WBTS counter measurement (M5000C153)
Check average or data volume HSUPA throughput from Cell Throughput measurement with RNC_952c
sum(NRT_EDCH_UL_DATA_VOL + RT_E_DCH_UL_STREA_DATA) * 8 / sum(PERIOD_DURATION)*1000000*60
Check HSUPA throughput from M5002 Cell Throughput_WBTS and its throughput distributions in classes
Counter
ID Measurement Counter name
M5002C41 Cell_Throughput_WBTS UE_HSUPA_TP03
M5002C42 Cell_Throughput_WBTS UE_HSUPA_TP04
M5002C43 Cell_Throughput_WBTS UE_HSUPA_TP05 Note: HSUPA cell throughput
M5002C44 Cell_Throughput_WBTS UE_HSUPA_TP06 measurement is less accurate
M5002C45 Cell_Throughput_WBTS UE_HSUPA_TP07 than HSDPA cell throughput
M5002C38 Cell_Throughput_WBTS UE_HSUPA_TP00 due to counters updating
M5002C39 Cell_Throughput_WBTS UE_HSUPA_TP01 across total measurement
M5002C40 Cell_Throughput_WBTS UE_HSUPA_TP02 period and not in active data
M5002C46 Cell_Throughput_WBTS UE_HSUPA_TP08 transfer period
M5002C47 Cell_Throughput_WBTS UE_HSUPA_TP09
M5002C48 Cell_Throughput_WBTS UE_HSUPA_TP10
M5002C49 Cell_Throughput_WBTS UE_HSUPA_TP11
M5002C2 Cell_Throughput_WBTS EDCH_DATA_SCELL_UL
M5002C3 Cell_Throughput_WBTS EDCH_DATA_NSC_S_EDCH_UL
EDCH_DATA_NSC_NS_EDCH_
M5002C4 Cell_Throughput_WBTS UL
Check HSUPA user throughput by dividing aboved with KPI RNC_1037a -Average number of simultaneous HSUPA users, during HSUPA
usage
Check CQI distribution (M5000C8-M5000C39) or Ecno distribution for bad coverage issue
(M1007C38-M1007C47)
Check If low throughput due to high number of retransmission & failed retransmission
(RNC_917a HSUPA MAC-es BLER)
Check KPI RNC_1165a/RNC_1166a for low HSUPA throughput due to Iub congestion
(frame delay or frame loss)
• Note: HSUPA throughput measurement is less accurate than HSDPA throughput due to
counters updating across total measurement period
95.0 2500000
90.0 2000000
85.0 1500000
Cell found
80.0 ISHO success ratio better 1000000
rate worse for for NRT
NRT
75.0 500000
70.0 0
6) 6) 6) 6) 6) 6) 6) 6) 6) 7) 7) 7) 7) 7) 7) 7) 7) 7) 7) 7) 7) 7) 7) 7) 7)
2 00 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200 200
8/ 9/ 9/ 0/ 0/ 1/ 1/ 2/ 2/ 1/ 1/ 1/ 2/ 2/ 3/ 3/ 4/ 4/ 5/ 5/ 6/ 6/ 7/ 7/ 7/
8/0 1/0 5/0 9/1 3/1 6/1 0/1 4/1 8/1 1/0 5/0 9/0 2/0 6/0 2/0 6/0 9/0 3/0 7/0 1/0 4/0 8/0 2/0 6/0 0/0
(2 (1 (2 (0 (2 (0 (2 (0 (1 (0 (1 (2 (1 (2 (1 (2 (0 (2 (0 (2 (0 (1 (0 (1 (3
0 06 006 006 006 006 006 006 006 006 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007 007
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
35 37 39 41 43 45 47 49 51 01 03 05 07 09 11 13 15 17 19 21 23 25 27 29 31
RNC_573a/ISHO cell found ratio, RT RNC_574a/ISHO cell found ratio, NRT RNC_300a/ISHO Success Rate RT
RNC_301a/ISHO Success Rate NRT RNC_298a/ISHO Attempts RT RNC_299a/ISHO Attempts NRT
U Node RNC CN
E B
RRC: Measurement Control
ISHO
RRC: Measurement Report triggering (5
NBAP: Radio Link Reconfiguration reasons are
Prepare possible)
NBAP: Radio Link Reconfiguration
Ready Initial
NBAP: Radio Link Reconfiguration Compressed
Commit Mode
RRC: Physical Channel
Reconfiguration Configuration
RRC: Physical Channel Reconfiguration
Complete
NBAP: Compressed Mode
Command
RRC: Measurement Control
GSM RSSI
RRC: Measurement Report Measureme
nt
NBAP: Compressed Mode Command
RRC: Measurement Control GSM BSIC
Identificatio
RRC: Measurement Report n
RANAP: Relocation
Required
RANAP: Relocation
Command
RRC: Handover from UTRAN
Command
RANAP: IU Release
Command
RANAP: IU Release
Complete
UE Node B RNC CN
RRC: Measurement Control
RRC: Measurement Report ISHO triggering (5 reasons are possible)
Low ISHO
CM Start
No Measureme
No No Low ISHO
Not
nt Success ?
Possible?
success ?
Yes
Yes Yes
50 -85
IS_COM_MOD_STA_NOT_P
40 OS_RT
-90
-100
20
-105
10 -110
2004090901
2004090902
2004090903
2004090904
2004090906
2004090907
2004090908
2004090909
2004090912
2004090914
2004090915
2004090917
2004090918
2004090919
2004090920
2004090922
2004090923
2004090900
2004090905
2004090910
2004090911
2004090913
2004090916
2004090921
0
20040907
20040908
20040909
20040910
20040911
20040912
20040913
20040906
hour
UE Failure
Counter
CN
RRC Drop
Counters IU Release Request
CN
T309
IU Release parameter
Request = 5 s (SIB1)
InterRATCellReselTmrOffset is hidden parameter 3s
RRC Drop
Counters
(XX=AMR,CS,NrtPS,RtPS)
3. Decision Algorithm
AdjgTxPwrMaxTCH
AdjgRxLevMinHO (n)
1. Triggering GsmMeasAveWindow
2. GSM measuring
3. Decision Handover Execution
2G-to-3G back prevention
GsmMinHoInterval
Soc Classification level
114 © Nokia Siemens Networks
4.ISHO Optimum Parameters based on experience
100%
90%
80%
70%
60%
50%
40%
30%
20%
10%
0%
02.03.2009
03.03.2009
08.03.2009
11.03.2009
12.03.2009
01.03.2009
04.03.2009
05.03.2009
06.03.2009
07.03.2009
09.03.2009
10.03.2009
13.03.2009
14.03.2009
15.03.2009
16.03.2009
ISHO NRT - Cell Found Ratio (574d ) ISHO NRT - Success Rate (301c) Cell Found x Success Rate
Number of defined
neighbours, max 32
Soc Classification level
119 © Nokia Siemens Networks
6. GSM ISHO Analysis & Optimization
• Normally ISHO has not been activated towards 3G, instead Inter RAT
cell reselection will happen to 3G in Idle mode
– bidirectional neighbour planning is used
– Max number of the adjacent GSM cells = 32
31 if Inter-system handover feature is activated
30 if there also any of Common BCCH features is activated
• 2G ISHO can/will be used to decrease GSM load
• It has be noticed that when there are small 3G coverage 2G ISHO will
happen successfully but then 3G ISHO will fail due to there is not enough
time for CM + BSIC verification -> 2G ISHO needs good 3G coverage
– ISHO cancellation in RU10 may cancel compressed mode in case one radio (if
in SHO) link is becoming better
Parameter full Name Parameter Name BSS Release MO class Range def. value Rec. value
THRESHOLD FOR MULTI-RAT MS QsearcC BSS11.5 HOC .0...15 15 7
MIN TRAFFIC LOAD FOR SPEECH CALL utranHoThScTpdc BSS11.5 HOC .0…100 % 80% 0-5
NUMBER OF MEASURED FDD CELLS fddMultiratRep BSS11.5 HOC .0...3 2
MIN INTERVAL BETWEEN UNSUCC ISHO ATTEMPT minIntUnsuccIsho BSS11.5 HOC 0..255s, step1 s 3
ADJACENT WCDMA RAN CELL AVERAGING WINDOW SIZE utranAveragingNumber BSS11.5 HOC 1..32, step1 6
NUMBER OF WCDMA RAN ZERO RESULTS noOfZeroResUtran BSS11.5 HOC 0..32, step1 5
ALL ADJACENT WCDMA RAN CELLS AVERAGED alladjacentCellsAveraged BSS11.5 HOC 0 (false), 1 (true) FALSE
INTER-SYSTEM DIRECT ACCESS LOAD THRESHOLD interSystemDaLoadThr BSS11.5 HOC 0..100 %, step1 50%
INTER-SYSTEM DIRECT ACCESS ENABLED interSystemDa BSS11.5 HOC 0 (false), 1(true) TRUE
TRIGGERING RATIO FOR WCDMA RAN CELL PENALTY FailMoveThreshold BSS11.5 HOC 0..100 %, step1
WCDMA RAN CELL PENALTY wcdmaRanCellPenalty BSS11.5 HOC 0..255, step1 127
MINIMUM CPICH EC/IO LEVEL minEcnoThreshold BSS11.5 ADJW .-24…0.5 dB -15 -8
DIRECT ACCESS EC/IO THRESHOLD intSystemDaecioThr BSS11.5 ADJW .-24…0.5 dB -11.5
Penalty Trigger Measurement Period TriggerMeasPeriod BSS11.5 BSC 2s..254s, step2s 128
Early Sending Indication earlySendingIndication BSS11.5 BTS 0 (No), 1 (yes) 1
FDD reporting threshold 2 FddRepThr2 BSS13 HOC .-115..-53 dBm -105
Handover
HandoverDecision
Decisionisisdone
doneinincase
caseof
of
•• Higher
Higher intra GERAN HO failed butload
intra GERAN HO failed but loadof
of BSS20967:
serving cell < Load_T hreshold
serving cell < Load_Threshold Coverage
•• LL
oad
oadofofthe
theserving
servingcell
cell>>LLoad_T
oad_T hreshold
hreshold based ISHO
for Voice
•• and CPICH Ec/No> min Ec/No Threshold
and CPICH Ec/No> min Ec/No Threshold
Handover
Handovercommand
commandisissend
sendto
toMSC
MSC
No Yes
Rn (GSM) > Rs (WCDMA)
And
Rxlev (GSM) >QrxlevMin
CPICH Ec/No
FDD_Qmin >= QqualMin + Ssearch_RAT
UE
UEwill
willre-select
re-selectWCDMA
WCDMAcellcellinincase
caseit's
it's
quality is acceptable:
quality is acceptable:
FDD_Qmin >=-10
CPICH Ec/NoMinimum_FDD_Threshold
CPICHEc/No Minimum_FDD_Threshold
QqualMin + Ssearch_RAT
= -14dB
QqualMin = -18dB
t
Camping in 3G Camping in 2G Camping in 3G
The “rule” to set the FDD_Qmin value has not Fdd_Qmin mapping
been possible to be fulfilled until the Aif parameter 0 1 2 3 4 5 6 7
specification change (05.08 v8.18.0, 2003-8) Fdd_Qmin (old) [dB] -20 -19 -18 -17 -16 -15 -14 -13
has been implemented to the UEs – as below Fdd_Qmin (new) [dB] -20 -6 -18 -8 -16 -10 -14 -12
• RRC connection request amount for inter RAT cell reselection ratio to
all RRC Connection request causes
• When Treselection is increased this KPI should decrease
M1001C42 INTR_RAT_C ELL_RE_SEL_ATTS
M1001C0 RRC_CONN_STP_ATT
80%
60%
40%
20%
0%
6/19/2007 6/20/2007 6/21/2007 7/10/2007 7/11/2007 7/12/2007
BEFORE AFTER
85-100% 1 1
70-85% 3 7 1 1 Decreasing
50-70% 12 10 9 7 6 8
<50% 41 39 47 50 51 48
Cluster JBK09 Percentage Distribution
Comparison Date after implementation:
☺Decreasing black and red colour as high percentage of Inter Rat Cell
Reselection
☺Increasing green colour as low percentage of Inter Rat Cell Reselection
Soc Classification level
135 © Nokia Siemens Networks
7. Cell Reselection 3G & 2G
• For the the camping in indoor environment the set-up could be :
• Indoor GSM / Outdoor GSM (serving indoor)-> Indoor WCDMA / Outdoor
WCDMA (serving indoor)
• Mobile station measuring WCDMA neighbor only when it is well inside the
building using parameter Threshold to search WCDMA RAN Cells
• The defined set-up can be also used in outdoor environment to push the
UEs to 3G as soon as possible from the 2G cell to the border 3G cell
• Process flow
FDD_RSCP_Threshold >=
- 100dBm
Qrxlevm in+Pcom pe nsa tion +SHCS_RAT
SHCS_RAT=1 0 dB