2G-3G KPI’s Improvements

Key points

1 © 2017 Nokia
Nokia Radio & System Modules Details

System Module

FSMF

Radio Module for 2G

FXEF for 1800 Freq & FXJB for 900 Freq

Radio Module for 3G

FRGU its supports both 3G & 4G same band (2100). Power supports 20W & 40W, its supports 5MHz & 10MHz of channel bandwidth.
FRGX its supports single band (2100). Power supports 20W & 40W.
FBBC is child card its use for port connection and sector additions.

Capacity:-

FSMF 512 Channel Elements

R99 168 Channel Elements
HSDPA 72 Users (Processing set 2 or 3 elements License oriented)
HSUPA 24 Users (Processing set 2 or 3 its support up to 6 License oriented)
FBBC258 Channels elements its used for sector additions and RF port EXT connections
3G KPI Improvements Key Points
3G Over View:-

Accessibility: Retainability

 RRC Setup & Access Rate  RRC Drop Rate

 RAB Setup & Access Rate  RAB Drop Rate
 Call Setup Success Rate  Packet Success Rate (HSDPA & HSUPA)
 Packet call setup success Rate (Non-Real Time, HSDPA & HSUPA)

Usage: Mobility

 Cell Availability SHO/ISHO Success Rate

 Average Uplink load  Soft Handover Success Rate
 Average Downlink load HSDPA & HSUPA Success Rate
 Hsdpa Throughput
 Cell Throughput
 Payload (DL+UL)

Netact Reports of 3G:-

 RNC Capacity  RSRAN068

 Accessibility  RSRAN073
 RetainabilityRSRAN079
 Traffic (R99+HSDPA)  RSRAN070
 RRC Signalling RSRAN038
 Real & Non-Real Time Traffic RSRAN078
 SHO ReportRSRAN045
 ISHO ReportRSRAN056
 FramelossRSRAN143.
3G KPI Improvements Key Points
Call Setup Success Rate (CSSR):-

I. Good RF conditions
II. Admission Control can reject too many (or admit too many) connection requests due to wrong PrxNoise measurements.
III. PrxNoise statistics, receive link parameters and HW units to be checked
IV. Poor coverage or dominance or interference issues in Radio interface
V. Capacity issues in Radio or Iub interface
VI. Configuration issues in WBTS (parameters or HW) CSSR is essentially RRC Setup Success * RAB Setup Success
(or successful PS session setups in case of PS call) CSSR covers all the steps from the initial RRC connection request from the
UE to the network, through the RRC setup phase and the RAB setup phase, and until user data is starting to get transferred

Reports Name:-
• Accessibility report for RSRAN073
• Retainability report for RSRAN079
• Frame loss & EDCH Frame loss RSRAN143
• RRC_Signaling for RSRAN038

KPI Counters for CSSR:-

• CS Voice Calls (RNC 565f)
• CS Video Calls (RNC566e)

Formulas for CSSR:-

servlev.rrc_conn_stp_rej_emerg_call)),0,null, (100*((servlev.moc_conv_call_atts - servlev.moc_conv_call_fails + servlev.mtc_conv_call_atts -
servlev.mtc_conv_call_fails + servlev.emergency_call_atts - servlev.emergency_call_fails - servlev.rrc_acc_rel_emergency -
servlev.rrc_acc_rel_mo_conv - servlev.rrc_acc_rel_mt_conv) / (servlev.moc_conv_call_atts + servlev.mtc_conv_call_atts +
servlev.emergency_call_atts - servlev.rrc_att_rep_mo_conv - servlev.rrc_att_rep_mt_conv -
3G KPI Improvements Key Points
Soft Handover (SHO):-

I. Cell Availability (Serving site and Neighbour sites)

II. Get system report for SHO (RSRAN046) and neighbour sites getting attempt vs success
=(R3/100)*N3 for success & =N3-O3 for fails
III. Neighbour audit not performing < 1 attempt remove from the target list.
IV. Site audit and physical optimization required.
V. Check the LAC & RAC combination for target cells.

Report Name for Handovers:-

• RSRAN046 for SHO

• RSRAN045 for ISHO.

Voice Drop:-

I. Cell availability (Serving site and Neighbour sites)

II. Poor coverage could lead to SHO, although poor dominance or interference can cause SHO to fail.
III. Rapid field drop can cause drop due to coverage
IV. Sudden drop to idle mode (no disconnect messaging)
V. Cause of the failure:
VI. overshooting site and SC reuse Short term solution to add overshooting neighbour in ADJS definitions

Reports for Voice Drop:-

• Use system reports in Netact saved reports (Reg Analysis 3G)

3G KPI Improvements Key Points
Throughput & Payload Improvements:-
2G KPI Improvements Key Points
Call Setup Success Rate (CSSR):-

I. Good RF conditions
II. Poor coverage or dominance or interference issues in Radio interface
III. Capacity issues in Radio or Iub interface
IV. Check hardware alarms

Handover Success Rate (HOSR):-

I. Cell availability (Serving site and Neighbour sites)

II. Neighbour audit required ADCE and ADJG (MCC,MNC,LAC & RAC Combination)
III. Should be check in in RSBSS153 report and remove unwanted neighbour from the neighbour index.

Source Target
Segment ID A tt (c15001) Blck Fail Fail Blck A tt (c15003) CI
A TT_TO BLCK_19 HFR_58 HFR_59 BLCK_20 A TT_FROM
17732 336 0.00 99.11 0.00 0.00 0 17754
17731 154 0.00 27.27 6.98 0.00 43 17732

HOSR TCH Drop

1 9 :0 0

2 0 :0 0

2 1 :0 0

2 2 :0 0

1 9 :0 0

2 1 :0 0

2 2 :0 0

2 3 :0 0
2 3 :0 0

2 0 :0 0
Cell Id Hourly Cell Id Hourly

08-Apr 93.10 86.67 100.00 100.00 100.00 08-Apr 12.27 13.64 1.00 0.98 0.91
17731 17731
09-Apr 90.70 99.31 96.65 100.00 100.00 09-Apr 1.76 2.13 1.26 0.00 0.00
08-Apr 58.00 46.43 66.67 45.00 25.00 08-Apr 3.28 2.13 0.00 0.00 0.00
17732 17732
09-Apr 89.47 100.00 95.65 100.00 100.00 09-Apr 0.00 0.33 0.00 0.00 0.00
2G KPI Improvements Key Points
SD DROP:
When SD is assigned for a mobile during call connection process and during this time due to any problem or any mismatch occurs by whichS
D loss occurs, It is between allocation of SD and before TCH allocation.
Reason for SD Drop:
I. Overshooting
II. Shift the SD time slot
III. Interference
IV. It may be uplink or downlink issue in which cells foe UL put TMA in that cell and DL provide tilt
V. HW Issue
VI. Wrong parameter planning
VII. Bad coverage
VIII. MAIO mismatch
IX. High Pathless
X. High LAPD utilization
XI. Wrong Power control settings
Solution for Removal of SD Drop:
Interference:
XII. Check the BCCH Plan(C/I or C/A)
XIII. Co-BSIC & Co- BCCH
Overshooting:
XIV. LAC Planning
XV. If a cell is picking call from long distance, check the sample log according to TA
XVI. Cell orientation need to defined according to clutter
Bad Coverage:
XVII.If the drop call is due to low signal strength uplink, check the receive path of this particular TRX. Check receiver sensitivity,
VSWR, feeder connection and etc. Drops due to Low Signal Strength.
XVIII.If the drop call reason is due to low signal strength downlink, then, check the transmit path. Check cards, feeder and etc.
2G KPI Improvements Key Points
TCH DROP:
Drop during conversation is known as TCH drop. It takes place after connect ACK msg on TCH.TCH drop occurring.
For TCH drop first cross check the BCCH of that cell, hardware issue may be, change RXP and RLT value. Find out there is any interference ,
neighbor defined.
Reasons for TCH Drop:

I. Wrong Parameter Planning.

II. BAD HOSR.
III. Hardware Fault.
IV. High TR Fail.
V. Overshoot.
VI. Outage.
Solutions for removal of TCH Drop:
Check Parameter:

VII. Check the BCCH Plan (C/I or C/A), Co-BSIC & Co BCCH.

Check Overshooting:

VIII. If a cell is picking call from long distance, Check the sample log according to TA..
IX. Site Orientation.
X. Effective tilt should be check.
XI. Mount position should be check

Improve HOSR:
XII. Check the Hopping plan.
XIII. Check the Neighbor Plan
 THANK YOU

10 © 2017 Nokia