You are on page 1of 64

WCDMA : KPI ANALYSIS & OPTIMIZATION

Network planning& Optimization

Illustration on RAN KPI-RU20
RNC Accessibility: RRC Setup & Access Rate RAB Setup & Access Rate Call Setup Success Rate PS setup success rate (NRT,HSDPA, HSUPA) SRNC Usage: Cell Availability Ave. Uplink Load Ave. Downlink Load HSDPA Throughput Cell Throughput SRNC Relocation RNC

UE

BTS2

X

Preemption

BTS1

Retainability: RRC Drop Rate RAB Drop Rate PS success rate (NRT, HSDPA, HSUPA)

X

Mobility: SHO/ISHO Success Rate SHO Overhead HDSPA/HSUPA SCC success / Date Presentation / Author rate

Genuine Call Setup Failure Scenarios
– RF issue

• Interference / Dominance / Coverage
• Missing neighbour

– System Issue - BTS

• No response to “RRC Connection Request” • “RRC Connection Reject” to “RRC Connection Request”
– System issue - RNC

• “CC Disconnect” after “Call Proceeding” due to “DL RRC Connection Release”
– Core NW

• “CM Service Abort” after “CM Service Request”
– System issue (test number)

• “CC Disconnect” after “CC Progress”

no disconnect messaging System issue RNC – Sudden “CC Disconnect” due to “DL RRC Connection Release” .Genuine Drop Call scenarios RF issue – Interference / Dominance / Coverage – Missing Neighbours System issue BTS – Sudden “CC Disconnect” due to “DL RRC Connection Release” – Sudden drop to idle.

HSDPA.The KPIs to be monitored from the RAN could be: – Cell availability – Call Setup Success Rate (CSSR) – Call Drop rate – SHO/ISHO/HSPA SCC success rate – Packet Session setup/success rate (NRT. HSUPA) In NOLS: – RNC counter description – NetAct DB description for RNC measurements – WCDMA RAN Key Performance Indicators – Key Indicator Changes – Measurement Changes KPI Definitions Presentation / Author / Date .

Service Established 7. Cell search. Branch addition/deletion & Active set update 8. Service Released . RRC connection set-up 3. BCCH decoding & RACH access 2. UE <--> CS-CN Signalling 6. UE <--> CS-CN signalling 4. RAB set-up 5.AMR CS Call Phases UE WBTS DRNC SRNC CN 1.

Call Setup Failure Analysis Process__DT Start A No Missing Neighbour ? No Yes No Yes Best server’s RSCP > -102dBm Coverage Optimization Dominance Optimization Best server’s Ec/No > -12dB Yes Neighbour list Optimization B UL coverage & RACH parameter. Optimization (changing serving cell) No AICH(ACK) received? Yes “RRC Connection Setup” received? Yes No Report & Finish (Check failure cause) No “RRC Setup Reject” received? Yes C D Report & Finish (Reason of problem: L1 sync fail) No (DCH) “RRC Connection setup Completed” sent from UE? AC optimization (check PrxNoise & interferer around BTS) Report & Finish Yes Report & Finish (Check failure cause) No “Radio Bearer setup failure”Received? Ye s E Report & Finish Check failure cause (Not radio problem/cell update) .

Call setup failures – Missing A Neighbour
Missing neighbour analysis over the whole route (3G-3G, 3G-2G) Search for failures due to missing 3G3G neighbours Search for failures due to missing 3G – 2G neighbours
– It is suggested to place 2G scanner to the test vehicle

Call Setup Failure Analysis-B Block B The purpose of this activity is to check the Random Access Process is working adequately by investigating whether AI (Acquisition Indicator) has been received through DL AICH If AICH was not received by UE, the cause of the problem can be classified into:
– Inadequate RAN parameter related to Random Access: RAN parameter

Call Setup Failure Analysis-B RNC WBTS UE Block B Preamble/RACH Acquisition Indicator/AICH RRC: RRC Connection Request/PRACH
NBAP: RADIO LINK SETUP REQUEST NBAP: RADIO LINK SETUP RESPONSE

RRC: RRC CONNECTION SETUP/FACH L1 Synchronisation
NBAP: SYNCHRONISATION INDICATOR

RRC: RRC CONNECTION SETUP COMPLETE/DCH UE in CELL_DCH state

RACH Process Downlink BS Not detected UEtxPowerMaxPRACH PowerRampStepPRACHpreamble B L1 ACK / AICH …… Uplink MS Preamble Preamble 1 2 …… Message part PowerOffsetLastPreamblePRACHmessage PRACH_preamble_retrans # PRACH preambles transmitted during one PRACH cycle without receiving AICH response RACH_tx_Max # preamble power ramping cycles that can be done before RACH transmission failure is reported Initial preample power: •Ptx = CPICHtransmissionPower-RSCP(CPICH) +RSSI(BS) + PRACHRequiredReceivedCI .

Call Setup Failure Analysis-B Block BSolutions for RACHNo To increase PRACH_Preamble_retrans optimisation Max UE Tx power hit To increase PRACH_Preamble_retrans the UE_P_MAX(24dBm)? Or PowerRampStepPRACHPreamble Or PowerRampStepPRACHPreamble Yes Yes Is UL Interference abnormally HIGH? Report there might be an interfering Report there might be an interfering source Nearby the serving cell source Nearby the serving cell No Change the Serving cell to cover the problem Area Change the Serving cell to cover the problem Area => UE is too far to reach the serving cell => UE is too far to reach the serving cell .

Call Setup Failure Analysis-B Block B Open loop Power Control parameters from RACH Info message .

wrong MHA parameters.Call setup failures – System C No response to “RRC Connection Request” issue BTS – Good RF conditions – Wrong MHA settings or cable loss settings can cause the site not to “hear” the UE – PrxNoise statistics. faulty units) . receive link parameters and HW units to be checked (faulty MHA. wrong cable / feeder loss parameters.

– PrxNoise statistics.Call setup failures – System C issue BTS “RRC “RRC Connection Reject” after Connection Request” – Good RF conditions – Admission Control can reject too many (or admit too many) connection requests due to wrong PrxNoise measurements. receive link parameters and HW units to be checked .

AC can reject RRC reject RRC connection Setup due the DL Load.e. UL load or DL Spreading codes – Marginal Load Area: • If measured UL (PrxTotal) or DL (PtxTotal) load exceeds target thresholds (PrxTarget and PtxTarget) AC can still admit new RAB to the cell if a new non-controllable load keeps below target thresholds (in practice this means that AC can admit only new controllable load RABs i. Call setup will fail.C Call Setup Failure Analysis UE has the appropriate DL/UL coverage but if RNC does not allow to set up the RRC connection of the requested RAB (Radio Access Bearer). Admission Control (AC) is involved in RRC connection setup. NRT RABs) – Overload Area: • If measured UL (PrxTotal) or DL (PtxTotal) load exceeds .

C Call Setup Failure Analysis .g. • If UL AC does not allow RRC setup: Check out if there is an interfering source nearby the serving cell.g. Signaling messages. it should be checked that measured PtxTotal and PrxTotal are less than PtxTarget (e. • If DL AC does not allow RRC setup check the Tx power of WBTS.• During the pre-optimization phase it is unlikely that AC will stop an RRC connection setup during the drive testing because there are normally very few UEs in the network. 40dBm) and PrxTarget (e. # of channels transmitted. (Traffic loading is trivial) • However. 60% loading) respectively. 4dB.

D Call Setup Failure Analysis To check if Layer 1 Synchronization (slot/frame sync) has failed If “RRC Connection Setup” was received by UE but UE does not send “RRC Connection Setup Completed”. . we will report “L1 synchronization failure” and have to check L1 system messages.

Call setup failures – System E issue RNC • “CC Disconnect” after “Call Proceeding” • Good RF conditions • Failures in RAB setup occur between the “RAB Assignment Request” being received from Core Network and the RAN sending out Radio Bearer Setup. Therefore the failure is between BTS and Core Network. .

• Call setup failures – System E issue RNC “CC Disconnect” after “Call Proceeding” (cont. • • .) An example (site shows high values on counter “RAB_STP_FAIL_CS _VOICE_BTS” during the drive test In the recent check the counter showed no failures.

. E UE Node B RR C Connection E stablishment RNC MGW Initial Direct Transfer (CM Service Request) SC CP : Connection R equest S CCP : Connection Confirm Location Reporting Control Common ID S ecurity Mode Command • R R C: Initial Direct Transfer message is sent using acknowledged mode R LC to the CS core domain.Call setup failures – Core “CM Service Abort” after NW “CM Service Request” Good RF conditions “Security Mode Command”-message not received by UE. same as the source reference within the Connection Request message • The Connection Confirm message identifies the RNC with a destination local reference w the hich is • The Connection Confirm message identifies the CS core with a source local reference • The CS core sends a RANAP: Location Reporting Control message to the RNC requesting information regarding the location of a particular UE • The RANAP: Common ID message specifies the IMSI belonging to the UE • The Security Mode Command message triggers the start or stop of ciphering and integrity protection. The NAS the m message includes the IMSI as a UE identity • The SCCP : Connection R equest message establishes the connection orientated signallingn link i the same way as it was for the R RC connection phase. Routing is to be based upon the local P -TMSI • The NAS message is not read by the RNC but is forwarded to ultimedia gateway.This does no t reserve any resources for the AMR call itself. thus the failure is believed to be at Core Network.

A static test was done by Nokia Customer Care and in few instances the call dropped after 30 seconds of recording passed.Call setup failures – System E “CC Disconnect” after “CC (test number) Issue Progress” Cause: recovery on timer expiry The call goes via IN SCP to a recording. Hence the problem is associated with the test number not the RAN 30 sec Cause: recovery on timer expiry .

Reconfiguration Frequent cell updates After RT call with inactive PS RABs UTRA RRC Connected Mode Fast call setup from CELL_PCH Phys. paging RB. Reconfiguration URA Update. Reconfiguration Cell Update. Paging URA_PCH CELL_PCH Fast call setup from URA_PCH After RT call with inactive PS RABs & high mobility in CELL_DCH CELL_DCH Phys. UL data. Reconfiguration UL/DL activation timer CELL_FACH Phys. Reconfiguration Traffic Volume. RACH load RRC Setup / Release RB. Overload IDLE Mode . Reconfiguration Inactivity Timer.State Transition triggers Phys. UL data.

2 sec DCH Transition DCH-FACH due to inactivity  10 sec )Parameter) FACH PCH FACH DCH Transition FACH-PCH du to inactivity  2 sec )Parameter) Wake up time PCH – DC due to activity  3 sec IDLE .State Transition triggers IDLE Call Setup 1.

• DCCH and – if configured – DTCH • Dedicate physical channel in use • UE location known on active set cell level • UE responsible for measurement reporting • Cell system information on BCCH • RRC messages on DCCH active set cell CELL_DCH State active set cell 25 © 2006 Nokia Layer 3 (RRC) / Kittipong Thamapa .

CELL_FACH State • DCCH and – if configured – DTCH • FACH used for higher layer data transfer. • UE monitors FACH permanently • Uplink transmission on RACH • UE location known on serving cell level • UE performs cell re-selection • UE responsible for measurement reporting • Cell system information on BCCH • RRC messages on BCCH. CCCH and DCCH serving cell 26 © 2006 Nokia Layer 3 (RRC) / Kittipong Thamapa .

UE location known on cell level .UE location known on URA level .UE performs cell re-selection and cell updates • In URA_PCH .UE performs cell re-selection and URA updates •one or several cells URA – UTRAN Registration Area •independent from LA URA 1 RNC supply area URA 2 27 © 2006 Nokia Layer 3 (RRC) / Kittipong Thamapa CELL_PCH no DCCH and DTCH and URA_PCH State • URA 3 .• Before uplink transmission ⇒ UE moves to CELL_FACH • UE must be paged • RRC messages on BCCH and PCCH • In CELL_PCH .

RU20 New Counters & Measurements / .

This counter is used as a denominator for cell availability calculation • Counter is updated with the value 1 one in approx. 5 seconds when the WCELL is configured in the radio network database Presentation / Author / Date . 5 seconds when the WCELL is in WO State M1000C180 AVAILABILITY WCELL EXIST IN RNW DATABASE • # of samples when WCELL is configured in the database.Cell Availability RNC_183c Cell Availability KPI counts Cell availability from user point of view: Cell _ Availability = 100 * sum( AVAIL _ WCELL _ IN _ WO _ STATE ) sum( AVAIL _ WCELL _ EXIST _ IN _ RNW _ DB ) M1000C178 AVAILABILITY WCELL IN WORKING STATE • # of samples when WCELL is in WO State. Counter M1000C180 is always updated along with this counter • Counter is updated with the value 1 once in approx.

Cell Availability – There is also Optional Cell availability KPI. which counts Cell Availability from network point of view. Counts Cell availability from network user _ excluding _ BLU _ state =  AVAIL _ WCELL _ EXIST _ IN _ RNW _ DB  sum  − AVAIL _ WCELL _ BLOCKED _ BY _ USER   point of view:   M1000C179 AVAILABILITY WCELL BLOCKED BY USER • # of samples when WCELL is BLU State. – RNC_727a Cell Availability KPI. Counter M1000C180 is always updated along with this counter • Counter is updated with the value 1 once in approx. 5 seconds when the WCELL is in BLU state Presentation / Author / Date . (excluding blocked _ STATE ) 100 * sum AVAIL _ WCELL _ IN _ WO by Cell _ Availabilitystate (BLU). Situation where WCELL is blocked by User are excluded from the formula.

CSSR definition DNO Optimization Processes / JC Ejarque .

Low in CSSR? Call Setup Phases Identify call setup failure phases CSSR affected if any of the followings take place. Access Fail 3. Act Connected RAB Setup RAB Drop DNO Optimization Processes / JC Ejarque . RRC Conn. RAB Setup Access Fail Call Setup Success Call Drop Call Setup Phase RRC RRC RRC RRC Conn. Req Conn. Setup Fail 2. RRC Conn. Setup Conn. 1. Acc Conn. RAB Setup Fail 4.

Low in CSSR? RRC/RAB Setup & Access Analysis Process Flow Chart Top (N) RRC Setup and Access failures Cell and Neighbour Cells availability Alarms/Tickets Sites OK ? Yes Setup /Access setup Setup Failure Cause? RNC BTS/TRANS/FROZBS AC UL/DL Interference (DL codes) Access setup Troubleshooting Top (N) RAB Setup and Access failures Setup /Access Capacity Optimisation Access Yes SRNS Relocation troubleshooting 3G cell at inter-RNC border ? NO Interference RF Optimisation Coverage Coverage/Interf erence DNO Optimization Processes / JC Ejarque .

Call Setup Success Rate (CSSR) Poor CSSR could be a result of – Poor coverage or dominance or interference issues in Radio interface – Capacity issues in Radio or Iub interface – 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. The CSSR formulas are for different traffic classes like: – CS voice calls (RNC 565 f) – CS video calls (RNC 566e) – PS RT Streaming Calls (RNC 575 d) – PS NRT Calls (Interactive & Background) (RNC 576d) Presentation / Author / Date . and until user data is starting to get transferred.

BTS. BTS. Transmission RRC Connection Setup phase RRC: RRC Connection Request Setup RRC Connection Access phase RNC waits reply from UE RRC: RRC Connection Completed RRC: Initial Direct Transfer cm service request DIRECT TRANSFER (Call Proceeding) RANAP: Initial UE Message RANAP: RAB Assignment Request Call Setup Success Rate Call Setup Time RRC: Radio Bearer Setup Resource Reservation in RNC. Transmission RAB Connection Setup phase RAB Connection Access phase RNC waits reply from UE RRC: Radio Bearer Setup Complete DIRECT TRANSFER (Alerting) DIRECT TRANSFER (Connect) DIRECT TRANSFER (Connect Acknowledge) Presentation / Author / Date RANAP: RAB Assignment Response .UE RRC: Connection Request Definition of Call Set-Up Success Rate (CSSR) BTS RNC CN Resource Reservation in RNC.

When an RRC active failure occurs. BTS. or Radio) or RNC internal failure occurs. AIR. Iur . the RRC send a RANAP: IU RELEASE REQUEST to all involved CNs and waits for RANAP: IU RELEASE COMMAND message (s) RRC: RRC connection Setup Complete RRC ACTIVE phase RRC: Initial Direct Transfer RANAP: Initial UE Message UE-CN Signalling (E. When an RRC setup failure occurs the RNC sends an RRC: RRC CONNECTION REJECT message to UE RRC ACCESS fails if the UE does not reply to RRC: RRC CONNECTION SETUP message with the RRC: RRC CONNECTION SETUP COMPLETE message in given time. Iub. and the failure causes the release of the RRC Connection. Transport) RRC: RRC connection Setup RRC ACCESS phase (RNC waits for Reply from UE) RRC: RRC connection Request RRC Setup time RRC SETUP fails if some of the needed resources (RNC. RAB Establishment and Release) RANAP: Iu Release Command RRC: RRC connection Release RRC: RRC connection Release Complete Release RRC resources in RNC. Transport) are not available. BTS.g.UE RRC Connection Setup & Access and Active BTS RNC CN RRC SETUP phase (Resource Reservation in RNC. BTS. IFHO. if the BTS reports a radio link synchronisation failure or in an RNC internal failure occurs RRC ACTIVE fails when an interface related (Iu. SRSN relocation or preemption Presentation / Author / Date . Transport RRC ACTIVE release cause can be either ISHO.

the RNC sends a RANAP: RAB ASSINGMENT RESPONSE message to the CN with an appropriate failure cause. both the RRC connection and RAB connection (s) are released. AIR. and the failure causes the release of the RAB connection. BTS. Transport) RRC: RB Reconfiguration RRC: RB Reconfiguration Complete RANAP: RAB Assignment Response RANAP: RAB Assignment Request with IE: RAB Release RRC: Radio Bearer Release RRC: Radio Bearer Release Complete RANAP: RAB Assignment Response Release RAB resources in RNC. Transport) RRC: Radio Bearer Setup RAB ACCESS phase (RNC waits for Reply from UE) RAB Setup & Access and Active BTS RNC CN RAB Access failures are not so Common RAB SETUP fails if some of the needed resources (RNC. only the failed RAB connection is released. • If the UE has more than one RAB connection and the failure is not so critical that it would lease to an RRC Connection drop. The RNC sends a RANAP: RAB RELEASE REQUEST message to the CN and waits for a RANAP: RAB RELEASE COMMAND or RANAP: IU RELASE COMMAND from CN • Otherwise. or Radio) or RNC internal failure occurs. When a RAB access failure occurs. Transport) are not available. When an RAB setup failure occurs the RNC sends a RANAP: RAB ASSINGMENT RESPONSE message to the CN with an appropriate failure cause RAB ACCESS fails if the UE replies with an RRC: RADIO BEARER SETUP FAILURE message or the connection cannot be established in a give time. Iub. The RNC send a RANAP: IU RELASE REQUEST message to the CN and waits for a RANAP: IU RELEASE COMMAND MESSAGE from the CN RRC: RB Setup Complete RANAP: RAB Assignment Response RAB ACTIVE phase (User Plane Data Transfer) RANAP: RAB Assignment Request with IE: RAB reconfiguration RAB Reconfiguration Actions (Reconfigure RAB resources in RNC. BTS. BTS. Iur. UE-CN Signalling RANAP: RAB Assignment Request RAB SETUP phase RAB Setup time RAB Holding Time (Resource Reservation in RNC. Transmission Presentation / Author / Date .UE RRC Connection Active Phase. BTS. Immediately after this. the RNC sends also a RANAP: IU RELEASE REQUEST to the CN and waits for RANAP: IU RELEASE COMMAND message RAB ACTIVE fails when an interface related (Iu.

UE BS RRC Connection Request RRC Connection Reject Cause: congestion RNC ICSU overload Failure Counter M1001C618 .RRC connection set up failure o processingConnection unit RRC power on ICSU is rejected ICSU can not process the call coming call request can not be handled due to lack of ICSU processing No hand free” is RNC internal clear code.

Access Fail • RAB Setup Fail • RAB Setup Access Fail Success Setup failures (blocking) Presentation / Author / Date . If dropped. • RRC Conn. also active RAB is dropped. Setup Fail • RRC Conn. RAB setup Attempts to start the call RAB setup access RAB active phase UE has RAB connection CSSR affected if any of the followings take place.Call Setup Failures RRC and RAB phases Phase: Setup Access Active Active Complete Access Active Release Active Failures Access failures Setup Complete Attempts Access Complete RRC Drop RRC connection setup RAN resources are reserved for signaling connection between UE and RNC RRC access Connection between UE and RRC RRC active UE has RRC connection.

Call setup Success rate -CSSR / .

Call Setup Success Rate (CSSR) user perspective (RNC 565f) CSSR KPI for CS voice from end 100 * ( sum( MOC _ CONV _ CALL _ ATTS − MOC _ CONV _ CALL _ FAILS + MTC _ CONV _ CALL _ ATTS − MTC _ CONV _ CALL _ FAILS + EMERGENCY _ CALL _ ATTS − EMERGENCY _ CALL _ FAILS − RRC _ ACC _ REL _ EMERGENCY − RRC _ ACC _ REL _ MO _ CONV − RRC _ ACC _ REL _ MT _ CONV ) AMR _ CSSR = sum( MOC _ CONV _ CALL _ ATTS + MTC _ CONV _ CALL _ ATTS + EMERGENCY _ CALL _ ATTS − RRC _ ATT _ REP _ MO _ CONV − RRC _ ATT _ REP _ MT _ CONV − RRC _ ATT _ REP _ EMERGENCY − RRC _ ACC _ REL _ EMERGENCY − RRC _ ACC _ REL _ MO _ CONV − RRC _ ACC _ REL _ MT _ CONV − RRC _ CONN _ STP _ REJ _ EMERG _ CALL ) * ( sum( RAB _ ACC _ COMP _ CS _ VOICE ) sum( RAB _ STP _ ATT _ CS _ VOICE )) RRC part RAB part RRC request repetitions done by UE after RRC reject are excluded from denominator (not necessarily seen as failures from the user's perspective) – Emergency calls re-directed to GSM layer are excluded from denominator The occurred cell re-selections are subtracted both from the numerator Presentation / Author / Date and denominator because they are not considered as call attempts .

_PACKET CALL SETUP SUCCESS RATE Presentation / Author / Date .

Packet Call Setup Success Ratio [%] over the reporting period. The UE has made Author / Date connection via another cell and Presentation / a new RRC Attempts-counter is updated in the new cell for the new attempt.PS Call Setup Success Rate (CSSR) RNC_576d. . Includes both(MOC _ INTER _ CALL _ ATTS − MOC _Background PS calls Interactive and INTER _ CALL _ FAILS 100 * ( sum + MOC _ BACKG _ CALL _ ATTS − MOC _ BACKG _ CALL _ FAILS + MTC _ INTER _ CALL _ ATTS − MTC _ INTER _ CALL _ FAILS + MTC _ BACKG _ CALL _ ATTS − MTC _ BACKG _ CALL _ FAILS + EMERGENCY _ CALL _ ATTS − EMERGENCY _ CALL _ FAILS − RRC _ ACC _ REL _ INTER − RRC _ ACC _ REL _ MO _ BACKG ( sum( RAB _ ACC _ COMP _ PS _ INTER − RRC _ ACC _ REL _ MO _ INTER − RRC _ ACC _ REL _ MT _ BACKG ) + RAB _ ACC _ COMP _ PS _ BACKG ) PS _ CSSR = * sum( MOC _ INTER _ CALL _ ATTS + MOC _ BACKG _ CALL _ ATTS sum( RAB _ STP _ ATT _ PS _ INTER MTC _ INTER _ CALL _ ATTS + MTC _ BACKG _ CALL _ ATTS − RRC _ ATT _ REP _ INTER − RRC _ ATT _ REP _ MO _ INTER − RRC _ ATT _ REP _ MO _ BACKG − RRC _ ATT _ REP _ MT _ BACKG − RRC _ ACC _ REL _ INTER − RRC _ ACC _ REL _ MO _ BACKG − RRC _ ACC _ REL _ MO _ INTER − RRC _ ACC _ REL _ MT _ BACKG )) + RAB _ STP _ ATT _ PS _ BACKG )) RRC part RAB part RRC request repetitions done by UE after RRC reject are included in the formula * The occurred cell re-selections are subtracted both from the numerator and denominator because they are not considered as call attempts from mobile enduser point of view.

DL Power & Code occupancy if there is need to upgrade radio capacity RRC_CONN_STP_FAIL_BTS Evaluate NBAP counters (radio link reconf. Failures) and KPIs for troubleshooting BTS resources Check BTS configuration in terms of 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 until the problem is solved In case BTS is not responding delete and re-create COCO RRC_CONN_STP_FAIL_TRANS Evaluate Number of reconfiguration failure due the transmission Check COCO Configuration Expand the capacity or decrease the traffic offered to the site until the problem is solved 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 Communicate the problem to Care department RRC_CONN_STP_FAIL_RNTI ALLO FAIL RNC decides to reject RRC connection request due to RNTI allocation failure caused by RRMU overload DNO Optimization Processes / JC Ejarque Analysis .Low in CSSR: Failure Counters RRC Conn Setup & Access RRC_CONN_STP_FAIL_AC Check UL Interference.

Low in CSSR: Failure Counters RRC Conn Setup & Access Analysis RRC_CONN_STP_FAIL_IUB_AAL2_TRANS Updated when there is shortage or blocking of AAL2 resource A subset of RRC_CONN_FAIL_TRANS which include ERQ/ECF fail due to some reason such as DMPG problem in RNC + ERQ/ECF fail due to transport resource needed in RNC between RNC/MGW RRC_CONN_ACC_FAIL_RADIO Dominant failure causes due to wrong UL or DL coverage UL Coverage -> Check if cell is affected by an external interference (Thermal Noise measurements). DNO Optimization Processes / JC Ejarque . reduce N312 from 2 to 1 (depends on UE model) or tune CPICHToRefRABOffset vs. DL Coverage -> Tune SCCPCH Power if UE does not receive the RRC Setup Message -> If UE does not synchronize. Qqualmin (or Qrxlevmin) RRC_CONN_ACC_FAIL_MS UL Coverage -> Tune Cell Dominance (or CPICH) in order to balance UL and DL (if UL interference if not the cause). Check if cell is affected by an external interference (Thermal Noise measurements).

M1001C531-C533 Check COCO Configuration RAB_STP_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 Communicate the problem to Care department DNO Optimization Processes / JC Ejarque (I/B) domains . Add failures) and KPIs for troubleshooting BTS resources Check BTS configuration in terms of 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 until the problem is solved. DL Power & Code occupancy if there is need to upgrade radio capacity using the already distributed Nokia Capacity Check BO report. Check PrxTarget / PrxOffset / of the affected cells RAB_STP_FAIL_XXX_BTS Evaluate NBAP counters (radio link reconf.Low in& CSSR: Failure Counters RAB setup Access Fail Root Cause Analysis: RT and NRT RAB_STP_FAIL_XXX_AC Check UL Interference. In case BTS is not responding delete and re-create COCO 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.

DNO Optimization Processes / JC Ejarque .Low in Access Fail Root Cause Analysis: RT and NRT (I/B) CSSR: Failure Counters RAB setup & domains RAB_ACC_FAIL_XXX_UE Evaluate Cell resource Prx and Ptx parameters (same as RAB_STP_FAIL_XXX_AC Case) 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 Communicate the problem to Care department.

Availability. configuration and capacity SHO New site ? Analyse last detailed radio measurements 3G cell covers over a coverage hole ? RF and ISHO neighbour optimisation RF and IF/IS HO neighbour optimisation To p iss ue s Core: Inners / Outers audit 2G : TCH blocking 3G : Wrong N’ borgs definition YES No cell found ratio >40 % NO ISHO Success Rate < 95% 3G cell at inter-RNC border ? YES YES No cell found ratio > 90 % and enough ADJG Coverage issue (new site needed) DNO Optimization Processes / JC Ejarque .High in DCR? Top (N) drops Neighbours’ Performance (use SHO success per adjs counters to identify badly performing neighbours) & Map Traffic Cell and its Neighbour Cells availability Alarms/Tickets Site OK ? YES Configuration & Parameter audit NO Conf OK ? YES SHO Success Rate < 90%? NO ISHO ISHO Failures NO 3G Cell at RNC border? YES YES Iur performance Investigation Iur Audit adjacent sites for alarms.

Call drop analysis process Start SHO Failure Analysis Yes SHO Failed No ISHO Failure Analysis Yes ISHO Failed No No Best server’s RSCP> -102dBm No Coverage Optimization Missing Neighbour No Yes Dominance Optimization Neighbour list Optimization Best server’s Ec/No> -12dB B Investigate possible BTS or RNC problem A Presentation / Author / Date .

Check Iur Call Drop Analysis process – SHO Analysis Start Yes Inter RNC HO No Fix SC Clash Yes SC Clash No No DL ASU received Yes Check neighbor definition parameters C Yes Load Optimisation Congestion on target cell No DL Tx Power Max Yes No UE Tx Power Max Yes Uplink Interference No No Check RF Levels Yes Load Optimisation/ External Interferer D Yes CPICH Optimisation Link Unbalanced No Presentation / Author / Date .

Rapid field drop can cause drop due to coverage Poor dominance or interference can cause Compressed Mode (CM) to start even if RSCP is still good. although poor dominance or interference can cause ISHO to fail. Drop call failures – RF issue A Poor dominance causes Active Set update failures Presentation / Author / Date . In CM UE transmits with higher power (more interference) and spends less time on 3G (less accurate measurement reporting) Poor dominance or interference can lead to Active Set update failures and eventually to drop call.RF drops mostly due to poor dominance or interference Poor coverage could lead to ISHO.

Drop call failures – RF issue A DL synchronisation is lost -> UE has stopped transmitting TrChAgg and DL DPCCH BER high Presentation / Author / Date .

Drop call failures – RF issue Fairly good CPICH Pilot EcNo Transport Channel BER. Btw UE<->RNC (MAC layer) A Sometimes DPCCH BER (btw UE<>WBTS) can be a better indicator of what's happening to the dedicated channel than the CPICH EcNo. in particular in the case that power control may not be tracking well Presentation / Author / Date .

no disconnect messaging – Site malfunctions to be checked – In the example below site had faulty unit (WTR) Drop to IDLE Presentation / Author / Date .Drop Call Failures – System B issue BTS Sudden drop to idle.

next call on the same cell => no failure. good RF & BER Not able to add SC265 to Active Set.Drop Call Failures – System B DPCCH Issues RNC “CC Disconnect” due to BER “DL RRC Connection Release” No response to UL Measurement Reports In the example site had no alarms. Difficult to troubleshoot if the failure does not happen systematically => follow up in the next weeks drive / do a separate drive test in the area Sudden “RRC Connection Release” Presentation / Author / Date .

Drop call failures (SC conflict) Transport Sudden drop to idle channel mode (no disconnect messaging) Cause of the failure: overshooting site and SC reuse Short term solution to add overshooting neighbour in ADJS definitions BLER 100% C Cell ABC. SC258 Presentation / Author / Date .

Drop call failures – Uplink Interference UL interference from the SIB7 message D Presentation / Author / Date .

Sum of UL PC commands < 1500. PC frequency is 1500 Hz.Drop call failures – Link UL & DL Power Control commands can help indicating problems in link Balance balance. if the sum of UL PC commands is < 1500. UE not receiving all the PC commands. Presentation / Author / Date . thus ideally the sum of PC commands to increase or decrease power is 1500 E. UE spends time on 2G D UE RX power control message: DL reception weak -> UE is ordering WBTS to increase power.g. this would indicate UE is starting to loose synchronization in Compressed Mode there is less PC commands.

Service level. receive link parameters. then RNC Rule out BTS failures – Check the site performance from Counters (Iub. cell resources SHO. alarms – SC–reuse – UE performance ? Identified causes for Active Set Update failure – “Deaf” sites (PrxNoise) – Faulty HW – SC-reuse Presentation / Author / Date . etc) and that site is carrying traffic – PrxNoise.Drop call failures – System issue RNC or BTS ? “CC Disconnect” due to “DL RRC Connection Release” is just a consequence of failure which can be due to different reasons – From UE point of view L3-messaging does not identify the point of failure distinctly – BTS or RNC failure? => Suspect BTS first.

/ .

YES YES Low through put due to low Ec/No or CQI If low throughput due to low Ec/No or Poor CQI. Implement Changes No Optimisation Required NO Identify reason for low throughput if not RF • Mobility (cell change too frequent) • No HSDPA coverage • Iub / Iu User Plane Capacity • Other HSDPA users in Business Object report already delivered in same WBTS/Cell order to measure all Start Parameter • DCH traffic too High (DPA. Measurement tools etc. identify reason • Bad Coverage Planning • Quality issue due the neighbour planning • HSDPA Parameters are correctly set up • Change Antenna tilt etc.HSDPA low • Low HSDPA throughput root causes analysis process throughput? START OSS counters measurement data collection Identify Low throughput areas if exist NO If throughput is low in network level. related HSDPA Optimisation by HSDPA Priority) tuning throughput KPIs • HSPDA Mobility parameters (FMCS) • PtxMaxHSDPA (WCEL) • Dynamic Flow Control set to ON (WBTS) DNO Optimization Processes / JC Ejarque . the reason can be also FTP/HTTP server settings (fire wall).

System Program 2. Traffic 4. Mobility and Handover 5. Mobility and Handover 5.RU10 Reporting Suite • RNC level system program added • Corrections to Capacity report • Modifications to Service level report (Streaming class added+ some other RNC_169e:DR + GAN HO corrections) added. Service Level 4. Mobility and Handover 5. Mobility and Handover 5. Traffic 4. Traffic 5. Service Level 3. Capacity 2. Mobility and Handover 5. Mobility and Handover 5. Traffic 4. Mobility and Handover Report Name System Program RNC Level System Program Cell Level RNC Capacity Node B Capacity Cell Capacity NRT Radio Bearer Statistics Service/Session Accessibility Analysis Service/Session Retainability Analysis RAB Holding Times Service Summary Allocated Traffic Amounts (R99 + HSPA) Cell Data Volume and Throughput at RNC Traffic Summary Used CE Capacity per RB Type in RNC Utilization Shares of Total Traffic Allocation Amounts Active Set Size for NRT-RT Traffic HSPA Serving Cell Change IFHO Adjacencies Inter-System Handover per Cause Inter-System Handover Performance Inter-System Handover Reasons ISHO Adjacencies Load Based HO Related Resources Load Based IFHO/ISHO Performance Load Based IFHO/ISHO Triggering Service Based IFHO/ISHO Performance SHO Adjacencies Soft Handover Performance Report ID RSRAN084 RSRAN000 RSRAN068 RSRAN066 RSRAN067 RSRAN013 RSRAN073 RSRAN079 RSRAN021 RSRAN003 RSRAN070 RSRAN077 RSRAN026 RSRAN022 RSRAN071 RSRAN078 RSRAN033 RSRAN044 RSRAN019 RSRAN023 RSRAN018 RSRAN045 RSRAN047 RSRAN048 RSRAN049 RSRAN050 RSRAN046 RSRAN028 Presentation / Author / Date . but load & service based counters removed Report Topic Name 1. Capacity 2. Mobility and Handover 5. Mobility and Handover 5. Capacity 3. Service Level 3. Capacity 2. Mobility and Handover 5. System Program 1. Mobility and Handover 5. Mobility and Handover 5. Traffic 4. Service Level 3. Mobility and Handover 5.

Transport 8. HSPA 7. Transport 8. Transport 8. HSPA 7. HSPA 7. HSPA 6. Transport 8. Transport 8. Transport 8. Transport 7. Signalling Report Name ATM Interface Traffic Load ATM VCC Traffic Load ATM VPC Traffic Load FTM Packet Transport Performance FTM Performance Iu-PS Throughputs Iub Throughputs Traffic on AAL5 Traffic on ATM Layer Traffic on Physical Medium Sub-Layer Transport Resource Reservations Channel Switching and HSPA Layering CQI Distribution HSPA Code and Modulation Usage HSPA Power Distribution MAC-hs Efficiency MAC-hs Retransmissions by Code and Modulation Usage Number of HSPA Users and UE capability NBAP Signalling RRC Signalling Report ID RSRAN081 RSRAN083 RSRAN082 RSRAN076 RSRAN072 RSRAN064 RSRAN080 RSRAN031 RSRAN029 RSRAN030 RSRAN069 RSRAN075 RSRAN039 RSRAN034 RSRAN074 RSRAN040 RSRAN041 RSRAN051 RSRAN027 RSRAN038 Presentation / Author / Date . Transport 8. HSPA 7. HSPA 7. Transport 8. HSPA 7. Transport 8. Transport 8. Signalling 6.• Modifications to KPIs due to streaming class + 64 HSDPA users/cell RU10 Reporting Suite Report Topic Name 8.

/ .