Basics Of KPIs

Jump/Network Operations Portal NOP (intranet)Jump User Id:Includes counters, KPIs and also reports in Reporting Suite Jump password: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 requiredCell AvailabilityFailures due to Radio, BTS or transportHandover PerformanceTrafficCell ResourcesIub SignallingSome data is better analysed at RNC level->Here only the time evolution and RNC comparison is usefulFailures due the RNC, Iu, Iur Iur, Iu, Relocation SignallingMonitor Cell/Neighbour cells Availability - missing cell has impact to neighbouring cells performance also1. Assess weekly average PLMN KPI performance to identify KPIs below targetsStart 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/AreaCompare different RNC/Regions Performance3. Apply drill down approach to assess bad performing KPIs in WCEL levelIdentify the failure call phasesCategorizing failure ratio or distribution of each counters (Radio, transmission, BTS, RNC)Identify main cause of underperforming KPIs4. Prioritize analysisFilter using high number of failures or high number failure ratio (weighting)Identify top 20/50 worst cells5. Analyze failure distribution in the network topology (rural, RNC border, expressway)6. Propose Solution for cells having network KPIs below KPI targetsBecause of the large number of cells in the network, it is not feasible to analyse all the cells. Good methodology is to list top 10-20 worst cells per region and to build and follow an action plan on thoseThis required a part-time or dedicated tracking roleEither total number of failures or failure rate (%) could be usedCoverage hole, missing neighbour or capacity problemIn Loaded networks the Weekly Busy Hour CSSR is relevant The failures originate mostly from congestions (Iub, BTS HW (CEs), radio) The call blocking probability is designed for the BHIn 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 trafficIn 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 In example below, the PS Busy Hour is later in the evening (20-21 hours) than CS (15-16 hours). During weekend CS data drops significantly while PS data is quite constantThe new smart phones such as Blackberry (RIM), iPhone (Apple) and N97 (Nokia) are loading the network in a new wayApplications which require always on connectivity have become very popular in many networksFast dormancy or Quick Release will have impact to the load & performanceCall can be traced by using subscriber's IMSI, MSISDN or equipments IMEI number Subscriber trace can be used for:In system testing and provisioning phase for trouble shooting and network optimisation.

Accessibility1.1.1.1.1. Accessibility Analysis (CS/PS/HS)CS/PS Access Failure Optimization:Call Setup analysis

Call Setup Success Rate (CSSR)CSSR is essentially RRC Setup & Access Success * RAB Setup & Access SuccessPoor CSSR could be a result ofPoor coverage or dominance or interference issues in Radio interfaceCapacity issues in Radio or Iub interfaceConfiguration issues in WBTS (parameters or HW) Voice Access failure= RRC Setup & Access fails + RAB Setup & Access failsStarting criteria for setup failure analysis

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

2) Coverage or Interference-- Cell Power Reporta) Coverage-- best server RSCP should not be lesser than -102dbm----- Coverage Optimization-- PRACH_Propagation_Delay Reportb) Interference-- best server Ec/No should not be less than -12dbTilt- for Dominance OptimizationMissing neighbor checks-- for neighbor optimization3) AICH ACK. Received?----No (UL Coverage & RACH parameter Optimization)4) RRC Connection Setup Received?NO---a) RRC Setup reject msg. received---No (Check failure Cause) Yes (AC Optimization--- check PRx Noise & Interferer Around BTS)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.RRC_CONN_STP_FAIL_HC (very Minor)--- usually 0%

RRC_CONN_STP_FAIL_AC (dominant)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 ReportUL 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 ReportEvaluate NBAP counters (radio link reconfiguration failures)-- NBAP Signalling Per cause ReportExpand 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 ResetExampleRRC_CONN_STP_FAIL_TRANSShort One day dat-- to show top 10 sites having highest number of BTS failures Evaluate Number of reconfiguration failure due the transmission-- Traffic_on_Physical_Medium_Sub-Layer & Iub Capacity reportsMajority of BTS Failures is coming from few sites.Expand the capacity or decrease the traffic offered to the siteCheck CE usage for these sites - > add CE capacity if needed or try to reduce the usage For ATM based IubCheck COCO ConfigurationOne site detail analysis show that Average UL CE usage ratio is above 90% causing high blocking -> Capacity issue Use AAL2 Multiplexing in case of two WAMFor 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 reportSHO Branch setup fails BTS/Iub-- SHO Overhead Report--No. 88, trafficRNC capacity SW New DSP counters-- DSP Resource Usage, DSP State Changes- System reset/user reset & DSP_Service_Statistics reports

RRC_CONN_STP_FAIL_RNC Typically RNC fault or Incoming SRNC Relocation Failure (inter-RNC border)--- RNSAP/NBAP SignallingIur Troubleshooting-- RNSAP_Signalling ReportDMPG problem in RNCRequired ICSU log tracing if no RNC fault or SRNC relocation problem

RRC_CONN_STP_FAIL_ICSU_OVERLICSU overload

RRC_CONN_STP_FAIL_RNTI ALLO FAIL RNC decides to reject RRC connection request due to RNTI allocation failure caused by RRMU overloadYES---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---b)Ue fails--- c)RNC Internal fails--RRC Access failure reasons:RRC Active release can be due to-- ISHO, IFHO, SRNC Relocation, Pre-emptionRRC_CONN_ACC_FAIL_RADIO (Dominant failure cause type) Perform drive test to detect if UL or DL coverage Coverage or interference-- Cell Power ReportUL CoverageUL coverage(TMA/MHA chk), Interference-- Tilt / Missing Neighbor chk / best server Ec/No should not be less than -12dbDL CoverageTune SCCPCH Power if UE does not receive the RRC Setup Message from RNC./ Antenna tilt(CPICH RSCP should not be -2 dB->-4 for networks with lot of smartphones)RRC_CONN_ACC_FAIL_MSUL CoverageTune 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 areaPropagation delay counters from RRC measurement M1006C128-C148 reports call setup distance during RRC connection request or cell updateThis give hints that either cells has large coverage area (tall sites with over-shooting) or non-optimum cell coverage from neighbouring cells

Some more counters of RRC Access failsM1006C203RRC CONN REJECT DUE TO IUB OVERLOAD CTRLM1006C204RRC CONN REJECT DUE TO MAX REGISTRATIONSConfiguration & SW issuesM1006C205RRC CONN REJECT DUE TO CENTRALIZED UNIT OVERLOADM1006C206RRC CONN REJECT DUE TO BUFFER LIMIT CTRLM1006C208RRC CONN REJECT DUE TO RNC RESTARTWhen the RNC sends RRC CONNECTION REJECT message to the UE because the RNC has recently restarted and the maximum number of RRC connection establishments is limited until a guard timer expires.

Yes---RAB Setup failure received?---No ( chk failure cause) Yes (chk failure cause--Not Radio related Problem/Cell Update)

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 CNRAB Active fails occurs (due to Radio, Iu, Iur, Iub, RNC internal fails)-----

RAB setup & Access Fail Root Cause AnalysisRAB_CONN_STP_FAIL_AC (dominant)[ Admission control could reject establishment of new Connection/bearer ]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 ReportSetup Failures due Admission Control - ACUL Power Spikes -> Disable UL Admission Control to if the number of failures is critical (PrxTarget-> 30 dB), implement TN159Number_of_HSPA_Users_and_UE_capability reportRRC/RAB cs setup failures due AC - Admission control rejects the establishment of new RRC/RAB connection due the When HSPA is enabled in the cell, the DL and UL resources are shared between HSPA and R99 usersUL Power, DL Power and DL CodesBoth R99 and HSPA should be monitored-- Cell utilization + Allocated_Traffic_Amounts_(R99_+_HSPA) reportRAB PS setup failures due AC Admission control rejects the establishment of new PS radio bearer due the From the HSDPA side, besides of blocking, HSDPA throughput limitations can be also monitored-- Node B utilization/ HSPA Overview/UL power, DL Power, DL codes and too many users in the schedulerNumber_of_HSPA_Users_and_UE_capability/ MAC-hs_Retransmissions_by_Code_and_Modulation_Usage reportsHSDPA Access failures due the UL DCH AC rejects the establishment of new HSDPA connection (related to HSDPA UL return channel)RAB_CONN_STP_FAIL_BTS (dominant when HSDPA active)UL powerCheck BTS configuration in terms of CE allocation Use Channel Element (M5001) Counters in order to evaluate lack of Channel Elements-- NodeB Utilization/CE Utilization ReportHSDPA access failures due number of HSDPA users reached new HSDPA connection is rejected due too many HSDPA usersEvaluate NBAP counters (radio link reconfiguration failures)-- NBAP Signalling Per cause ReportExpand 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

RAB_CONN_STP_FAIL_TRANSCheck M1005C128 CANC_ADD_SRNC_TRAN_STP_FAILfailure)Evaluate Number of reconfiguration failure due the transmission-- Traffic_on_Physical_Medium_Sub-Layer & Iub Capacity reportsi.e. (The number of cancelled synchronised radio link reconfigurations on SRNC sideExpand the capacity or decrease the traffic offered to the site due to a transmission setup failure or RNC DMPG/DSP resource allocation)For ATM based IubCheck COCO ConfigurationCheck RAB_STP_FAIL_XXX_IUB_AAL2, M1001C531-C533 Use AAL2 Multiplexing in case of two WAMFor 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 reportSHO Branch setup fails BTS/Iub-- SHO Overhead Report--No. 88, trafficRNC capacity SW New DSP counters-- DSP Resource Usage, DSP State Changes- System reset/user reset & DSP_Service_Statistics reports

RAB_CONN_STP_FAIL_RNC Typically RNC fault or Incoming SRNC Relocation Failure (inter-RNC border)--- RNSAP/NBAP SignallingIur Troubleshooting-- RNSAP_Signalling ReportDMPG problem in RNCRequired ICSU log tracing if no RNC fault or SRNC relocation problem

RAB_CONN_STP_FAIL_ICSU_OVERLICSU overload

RAB_CONN_STP_FAIL_RNTI ALLO FAIL RNC decides to reject RRC connection request due to RNTI allocation failure caused by RRMU overload

RAB_ACC_FAIL_Iur trans--- RNC capacity ReportRAB_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

RAB_ACC_FAIL_XXX_MSEvaluate Cell resource Prx and Ptx (for example high uplink interference)--NRT_Radio_Bearer_stats report for Prx & Ptx ratio UL Coverage tuningCheck RB reconfiguration failure ratio ( If ATO setting is insufficient , rec. 500ms)--- RRC signalling report Tune Cell Dominance (or CPICH) if the cause is UL interference DL Coverage tuningTune SCCPCH Power if UE does not receive the RRC Setup Message from RNC.

RRC_CONN_ACC_FAIL_RADIO (Dominant failure cause type) Perform drive test to detect if UL or DL coverage Coverage or interference-- Cell Power ReportUL CoverageUL coverage(TMA/MHA chk), Interference-- Tilt / Missing Neighbor chk / best server Ec/No should not be less than -12dbDL CoverageTune SCCPCH Power if UE does not receive the RRC Setup Message from RNC./ Antenna tilt(CPICH RSCP should not be80-85%--- NodeB Utilization/CE Utilization Report)

Voice Drops due to RNCTypically RNC fault or Incoming SRNC Relocation Failure (inter-RNC border)--- RNSAP/NBAP SignallingRNC capacity SW New DSP counters-- DSP Resource Usage, DSP State Changes- System reset/user reset & DSP_Service_Statistics reportsIur Troubleshooting-- RNSAP_Signalling ReportDMPG problem in RNCRequired ICSU log tracing if no RNC fault or SRNC relocation problemICSU 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 TransRAB_ACC_FAIL_Iur trans--- RNC capacity ReportRAB_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 statisticsNeed Tilt / Azimuth change to improve the area? UL CoverageUL coverage(TMA/MHA chk), Interference-- Tilt / Missing Neighbor chk / best server Ec/No should not be less than -12dbCoverage or interference-- Cell Power ReportDL CoverageTune SCCPCH Power if UE does not receive the RRC Setup Message from RNC./ Antenna tilt(CPICH RSCP should not be 90%-- check ISHO failures?No ISHO failures--- new site needed?/ RF & IFHO Neighbor OptimizationYes ISHO failures (ISHO Reports)---Check No cell found ratio>40% or not?-- Inter-System_Handover_Performance reportIf No cell found ratio >40%-- 3G cell at inter-RNC border/ 3G cell covers a coverage hole---- RF & ISHO neighbor optimizationCheck missing neighbour/badly performing neighbors(ISHO Adjacencies 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 HOGSM 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 congestion4.Check ISHO KPI if RT ISHO < 90% or NRT < 80% (leads to radio failure)

If No cell found ratio is>90% & enough ADJIs--- Wrong reference Clock tuning( 10MHz tunning)If No cell found ratio CPICHToRefRABOffset, PTXDPCH MAXCheck Call reestablishment timer -> T315 (rec.10s)Ecno distribution for bad coverage issue (M1007C38-M1007C47)

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?

RRC active drops reasons:RAB AMR active drops reasons:Packet service RAB active, drops reasons:Packet session, drops reasons:IuIuIuHS-DSCH/E-DCH DR, RLIurIurIurHS-DSCH/DCH DR, RLBTSRNCRNCDCH/DCH DR, RLRNCMSMSHS-DSCH/E-DCH DR, OtherMSUEUEHS-DSCH/DCH DR, OtherCIPHCipheringTransTransDCH/DCH DR, OtherUERadio failsRadio failsTransRadio fails

R99 PS Drop Call Optimization:R99 is NRT service basicallyNRT 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 report2. BTS-- chk BTS HW resources-- NRT_Radio_Bearer_stats report for BTS congestionFailed SCC due to HSDPA return channel-- chk SCC fails-- Service_Session_Retainability report--for HS_DSCH SCC failsHSPA_Serving_Cell_Change report-- for reasons, causes, failsSCC=Serving Cell Change

3. Iu-- chk core network parameter settings---

4. Iur-- Inter RNC mobility?

5. RNC-- RNC Internal problem

6. UE-- Terminal problem

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

Packet Session AnalysisPacket call normal releases (normal end of the call) counters includes Transition to DCH 0/0, Cell_FACH or Cell_PCH due to inactivity or low utilisation Outgoing SRNC relocation Inter-RNC hard handover Inter-system Hard HandoverPacket call Failures are divided intoRL failsOther Non-RL FailsPre-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)HS-DSCH Allocation release

HSDPA Drop reasons: RL fails, Non-RL fails, Mobility fails, Pre-emption fails, other fails1. RL 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 DL coverage & Interference-- PRACH delay range report/tilt Neighbor Optimization etc.Iub -- HSPA Overview report-- for Iub congestionRAB_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 congestionIub_Traffic_-_FP_layer report-- for rejections, discarded frames & lost PDUs with reasonsCE 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)

ATO=Offset for activation time of SRBs on HSPA= 300 to 500msPtx target=40dbmPrxtarget=5dbm2. Non- RL Fails/Others-- CheckCPICH tx power= 35.1dbmUE responding with some failure msg or not responding to some msg, but no RL failure (timer expiry)Chk RNC fails & use RNC logging If requiredCheck RB reconfiguration, physical channel reconfiguration, NBAP RL reconfiguration failure rate 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 Check NBAP RL reconfiguration failure rate?NBAP_Signalling report-- Radio link - SRNC, Radio link - DRNC, RL setups/reconf fails for HSDPA MAC-d flowNBAP_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 ?

HSDPA Retainability The retainability of all successfully allocated E-DCH resources for NRT trafficE-DCH Allocation release

HSUPA Drop reasons: RL fails, Non-RL fails, E-DCH RelRate(HS-DSCH SCC), other fails

There are several reasons for HSUPA release:RNC_1108aE-DCH Rel due to RL FailuresRNC_1109aE-DCH Rel due to other failures

RL fail is incremented If: a radio link failure happens during HSDPA call uplink RLC unrecoverable error happens (Cell Update by UE) RLC-entity in RNC reports RLC protocol reset

Cell capacity report -- UL load- HSUPA Physical CH pwrHSPA serving cell change report -- HSUPA SCC- E-DCH down to DCH, Inter RNCSoft handover performance report -- HSUPA SHO Success RateHSPA 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)Number_of_HSPA_Users_and_UE_capability report -- hsupa simultaneous users, hsdpa/hsupa user distribution

Traffic_on_AAL5 report

Release due to RL Failure counters:M1022C57 PS_REL_RL_FAIL_HS_E_INT M1022C58 PS_REL_RL_FAIL_HS_E_BGRM1022C59 PS_REL_RL_FAIL_HS_D_INT M1022C60 PS_REL_RL_FAIL_HS_D_BGRM1022C61 PS_REL_RL_FAIL_D_D_INT M1022C62 PS_REL_RL_FAIL_D_D_BGRare incremented in case RL Failure is received from BTS and cannot be acquired back during specific timeRelease due to Other Failure counters:M1022C63 PS_REL_OTH_FAIL_HS_E_INT M1022C64 PS_REL_OTH_FAIL_HS_E_BGRM1022C65 PS_REL_OTH_FAIL_HS_D_INT M1022C66 PS_REL_OTH_FAIL_HS_D_BGRM1022C67 PS_REL_OTH_FAIL_D_D_INT M1022C68 PS_REL_OTH_FAIL_D_D_BGRare incremented in case the PS allocation is released due to any other reason expect normal, pre-emption or RL failure

SHO,ISHO,HSDPA SSCSHO success rateSHO success rate KPI (RNC_195a) is informing how many successful Active set updates we will have, compared to initial Addition/Replacement/Deletion requests. SHO Reports:Soft_Handover_PerformanceCell levelAS 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, BadSHO_AdjacenciesCell levelSHO 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)--- YesCheck if cells are at RNC borderYes-- (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 windowDetect badly performing neighbours using HO success rate per adjacency counters-- delete/create them again, check SHO OverheadFrom cell level report

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

High incoming HO failure rate in all ADJS check sync alarms Audit Adjacent sites for Alarms/capacity/traffic and visualization check with mapEvaluate HO control parameters and trigger threshold

Check if DL Active set update received(Active_Set_Size_for_NRT-RT_Traffic Report)No-- SC clash?---yes(fix SC clash)no --- congestion on target cell ( Load optimization)DL Tx power max.?---yes ( in this case; Link is unbalanced--- do CPICH OptimizationYes-- UE Tx Power max.?--- no(chk RF levels) yes( check Uplink interference? )If UL interference----load optimization/External Interferer

SHO based on DSR( Detected Set relation)-- Enabled in TMOIf UL SRB becomes overloaded, it can cause: Delayed HOs -> decreased KPIsNAS signaling problemsRRC signaling problemsThese problems can be avoided by optimizing the following parameters:Increasing ReplacementWindow Increasing ReplacementTime Changing the interval of the periodical reports

New value for ReplacementWindow for Event 1C must be set in relation to events 1A and 1BFMCS: increase ReplacementWindow The amount of the ReplacementWindow increase depends on AddWindow and DeletionWindow sizesNo exact value can be given.

FMCS: increase ReplacementTime to 640msUE measures CPICH Ec/N0 internally every 200msTherefore practical ReplacementTime parameter values are 0ms, 240ms, 640ms and above to optimally utilize averaging in the UEOther values just cause delay (for example 320ms compared to 240ms means extra 80ms delay)Reporting happens on occasions 0, 200, 400, 600This is valid also for event 1A and 1B

Periodical reporting parametersExample: SHO Parameters ChangedAdditionReportingInterval Replacement parameters were changed in live network in the RU10 pilot:ReplacementReportingInterval FMCS: ReplacementWindow 2dB -> 6dBDropReportingInterval (RU10 parameter)FMCS: ReplacementTime 100ms -> 640msIncrease the interval of the periodical measurements or disable periodicity to make reporting event basedAddition and drop parameters were:Event 1C measurements are long, each occupying 160-200ms air interface time FMCS: AdditionWindow = 4 dBIf the measurement interval is too short, the whole UL SRB bandwidth will be easily fully occupied by long measurement reportsFMCS: AdditionTime = 100 msRecommended way is to increase the interval from 0.5s to 1.0sFMCS: DropWindow = 6 dBFMCS: DropTime = 640 ms Periodical reporting intervalsAdditionReportingInterval = ReplacementReportingInterval = 0.5sDropReportingInterval = 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%.

ISHO Success RateThe 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 partsISHO success rate for RT services (RNC_300g)ISHO success rate for NRT services (RNC_301e)BSIC decoding need to be done in target GSM cell for RTBSIC decoding is not needed for NRT Cell found ratio for RT tells how easily target cell is found No Cell found ratio-- should not be greater than 40-50%.1. CM start possible?--No( Chk Admission Control rejection--> PRxTotal, PTxTotal)AC rejects CM request due to Interference(UL/DL)Radio Link(or physical channel) re-configuration failure--due to BTS/UE reasons--- ISHO is parallel procedure at the same time Yes-- ISHO measurement Success?yes---1. missing ADJG/bad performing neighbors(SR/Adjacency)-- ISHO Adjacencies report2. 2G neighbors BCCH/BSIC collision chk3. Alarm of reference clock in 3G or in 2G4. TCH Blocking/TCH congestion( target GSM cell is fully Loaded)/TCH failures/2G traffic/2G Hardware Alarm 5. Compressed mode parameter set checking

6. Too low ISHO triggering threshold

7. Strict ADJG minimum thresholdADJG RxlevMinHO--(here set as -95dbm)

8. Poor GSM Coverage

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-DPCHIf No cell found ratio >40%-- 3G cell at inter-RNC border/ 3G cell covers a coverage hole---- RF & ISHO neighbor optimizationIf No cell found ratio is>90% & enough ADJGs--- Wrong reference Clock tuning( 10MHz tunning)If No cell found ratio ISHO success rate improved a lot -> ISHO cell found ratio decrease4. Missing ADJG/bad performing neighbors(SR/Adjacency)-- ISHO Adjacencies report---> to be defined & corrected5. Compressed mode parameter set changes6. GSM Measurement reporting parameters changes7. Changes in Decision Algorithm parametersa) AdjgTxPwrMaxTCH-- Maximum UE TX Power on TCH(HCConfiguration)--------->If Max. Output power of UE is < value of AdjgTxPwrMaxTCH parameter; RNC adds Power diff(db) to AdjgRxLevMinHO -- 0...43 dBm, step 1 dBm ( set as 30dbm in TMO)b) AdjgRxLevMinHO (n)--- minimum required GSM RSSI level----------------------->GSM neighbor cell must exceed the RSSI level of AdjgRxLevMinHO-- for a handover to be possible----- ( set as -95dbm in TMO)c) GsmMeasAveWindow -- kitni measurement report se RNC avg GSM RSSI value for handover nikallegi---- 1...32 MeasRep, step 1 MeasRep, (6 in TMO)

ISHO Parameters

(XX=AMR,CS,NrtPS,RtPS)

1.Triggering Force Decode BSIC feature for NRT2.GSM measuringRAS06 ED2.1 feature 3.DecisionISHO success rate improved a lot -> ISHO cell found ratio decrease

Multiple BSIC identification RU20The 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.

Multiple BSIC identification can be enabled with The MultipleBSICIdent parameter which must be set to on to enable the feature across an RNCThe MaxBSICIdentTime parameter limits the maximum time for BSIC identification measurements per cell. If during this time no handover succeeded the handover attempt to GSM is finished. The MaxBSICIdentTime parameter must be configured with a value of greater than 0Suggested valued for testing of 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.

Feature is applicable to both CS and PS connections so parameter is applicable in both RT and NRT FMCG parameter sets (although BSIC verification is not always required for PS connections)

ISHO Failure Scenarios CM start not possible

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

1Determine SCC success rate, SCC failure rate and failure cause distribution2Check 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 failure3If high SCC_FAILED_due_to_AC Check target cells M1000C22 AVE_PTXTOT_CLASS_4 and M1000C20 AVE_PTXTOT_CLASS_3 if SCC failures due to the lack of DL power (SCC_Failed_due_to_AC) this is not visible in HSDPA accessibility KPICheck target cells number of simultaneous active HSDPA users4If high SCC_FAILED_due_to_BTS Check target cells M1002C416/424 SETUP_FAIL_BTS_HS_DSCH_XXXCheck target cells CE resource utilisation at BH using M5001 counters for lack of UL return channel resource Check NBAP Radio Link Reconfiguration Failure rateCheck SHO overhead all branches must have enough CE capacity if UE is in SHO when HS-DSCH allocation is started 5If high SCC_FAILED_due_to_UE Check target cells M1002C415/423 SETUP_FAIL_UE_HS_DSCH_XXXCheck RB reconfiguration Failure rateRequire ICSU troubleshooting for UE types monitoring6.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 transmissionCheck M1005C128 CANC_ADD_SRNC_TRAN_STP_FAILCheck 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

RNC_153b SHO SR, RTRNC_192b SHO SR, NRT3. Decision AlgorithmAdjgTxPwrMaxTCHAdjgRxLevMinHO (n)GsmMeasAveWindowUE Tx Power (Event 6A)Threshold:GsmUETxPwrThrXX L3 filter: GsmUETxPwrFilterCoeffHysteresis margin: GsmUETxPwrTimeHystData rate thresholdHHOMAxAllowedBitrateULUL QualityTimerULQualDetRepThresholdData rate thresholdHHOMAxAllowedBitrateULDL DPCH powerThreshold:GsmDLTxPwrThrXXData rate thresholdHHOMAxAllowedBitrateDLCPICH RSCP (Event 1F)Thresholds:HHoRscpThreshold HHoRscpCancelL3 filter: HHoRscpFilterCoefficientTimers:HHoRscpTimeHysteresisHHoRscpCancelTimeCPICH Ec/Io (Event 1F)Thresholds:HHoEcNoThresholdHHoEcNoCancelL3 filter:EcNofilterCoefficientTimers:HHoEcNoTimeHysteresisHHoEcNoCancelTime2G-to-3G back preventionGsmMinHoIntervalHandover ExecutionGsmMeasRepIntervalGsmNcellSearchPeriodGsmMinMeasIntervalGsmMaxMeasPeriod2. GSM measurement reporting

Para ChecksUsually operator maintains a list of planned values. If no planned value exists for a parameter, it can be compared to NSN default value or to the most common value in the network.Target is to find and correct discrepancies in the parameter settings.Discrepancy check can be limited to the most important objectsWBTS licenses Any errors or mismatches between planned setup, configured setup, and actual hardware on site may lead to performance degradation.-Baseband capacity (license controlled in FlexiBTS up to HW limit)WBTS configuration can be checked using WBTS site manager:Number and type of HSDPA schedulers-- HSDPA shared schedular(in TMO)--HSDPA 48 Users per CellWBTS configuration files can also be collected using a tool such as FileCollectorTool:Number of HSUPA schedulers-- (HSUPA Basic 24 users per BTS enabled in TMO)https://twiki.inside.nokiasiemensnetworks.com/bin/view/SEM/CommandlineTools -Local cell grouping and capacity allocation between local cell groupsIt collects site configuration data (including commissioning data and licenses) to xml files which can be mass post-processed.-Cell maximum RF powerCollecting the data takes quite long time as the tool automatically logs to every WBTS to copy the data, but it can collect all the files in background without user interaction.-Antenna line properties (MHA gain, feeder loss, RX diversity branch,)Example script for WBTS xml file mass analysis:Output data includes:BTS configuration (cells, carriers, HSDPA/HSUPA schedulers, )BTS HW (system modules, radio modules, WSPx/WPAx/WTRx cards)BTS licensesLocal cell group configurationMHA and antenna line data

Check allocation of local cell groups:Check HSDPA scheduler type and number: number of cells per LCGHSDPA scheduler type is defined in WBTS commissioning phase or by HSDPA shared scheduler license baseband allocation per LCGIf shared scheduler is used, the number of schedulers depend on Tcell parameter settings on the site. Is HSUPA enabled in the LCGWrong scheduler type may cause HSDPA setup problems due to too many users, or waste baseband capacity if schedulers are underutilized.Non-optimal LCG allocation can cause unnecessary blocking due to lack of baseband capacity in LCG or reduced HSUPA performance if unused baseband capacity is allocated to other LCG.

If shared scheduler is used, the number of schedulers depend on Tcell parameter settings on the site.Tcell (Frame timing offset of a cell)-- WCEL parameterEach cell in a BTS uses a BTS Frame Number (BFN) counter, which is delayed by a number of chips defined by the value of Tcell.Tcell is used for defining the start of SCH, CPICH, Primary CCPCH and DL Scrambling Code(s) in a cell relative to BFN. The main purpose is to avoid having the overlapping SCHs in different cells belonging to the same BTS. An SCH burst is 256 chips long.Group 1: Tcell values 0 (0 chips), 1 (256 chips) and 2 (512 chips)Group 2: Tcell values 3 (768 chips), 4 (1024 chips) and 5(1280 chips)Group 3: Tcell values 6 (1536 chips), 7 (1792 chips) and 8 (2048 chips)Group 4: Tcell values 9 (2304 chips)Cells composing a Dual Cell HSDPA cell pair must have the same Tcell value.

UE classes HSDPA categoryMajority of the HSDPA UEs are still category 1-6 five code UEs having max 3.6 Mbps throughputUE classes HSUPA categoryFor HSUPA, the majority of the Ues in our Example are Category 5 UEs supporting 2Mbps throughput and 10 ms TTI. Less than 30% of the UEs are category 6 UEs supporting higher uplink bitrates with 2ms TTI.

Propagation delay countersPRACH Propogation Delay report-- can be used to evaluate how far UEs are from the cellCan be used to detect overshooting sitesM1006C169 PRACH_DELAY_RANGE_VALUE Counter can be used to monitor value of WCEL parameter PRACHDelayRange when the last RRC Connection Request or Cell Update of the measurement interval was received. WCEL parameter PRACHDelayRange 1 (5 km), 2 (10 km), 3 (20 km), 4 (60 km), 5 (180 km) Classification criterias in the below table. Example: Antenna Tilt Excercise KPIs UsedThree main counters/KPIs was used for selecting the candidates for tilt:1) PRACH_distance > 10 km 2) CSSR_CS (Call set-up success ratio)3) RAB_CS_DR (RAB CS drops) Overshooting WCEL was found based on monitoring the three main KPIs.Then decide whether it needs to be dowtilted or neighbor relations needs to be modified. WCEl parameter-- Cell range- 5000, 10000, 20000 (mts)If Cell range is= 5000; 500021238.09m1 class=238.09mPRACH Propogation Delay reportIf Cell range is= 100001000021476.19m1 class=476.19mClass 0 to Class 20 tak hoti hai If Cell range is= 20000; 2000021952.38m1 class=952.38m

UE estimates CQI using available information on the channel quality.RSCPEc/N0HSDPA transmit power (signalled to UE)Retransmission rateEtc.

PtxCellMax 43 dbm40 dbm40 dbmPtxCPICH 33 dbm30 dbm33 dbmImpact of PtxCPICH power tuning CCCH total35.532.535.5Under isolated cell without any other traffic. HSDPA 15 code, 64QAM enabled, Category14 64QAM HSDPA UE used Available HSDPA pwr (W)16.48.26.5Both PtxCPICH 33 dBm and PtxCPICH 30 dBm measured. All other parameter remains untouched (PtxCellMax was 40 dBm in both cases)Gammafactor 0.50.50.5While decreasing CPICH tx power by 3 dB (from 33 dBm to 30 dBm)Ptx_Allowed HSDPA (W)8.24.13.2Ave reported EcNo decrease ~ 2.5 - 3 dB EcNo degradedMPO, dB (calculated)6.16.12.1Ave reported CQI increases only by ~ 1 - 1.5MPO from Nemo 662

Reported CQI can be improved by optimisation on DL RF quality and levelReported CQI can not be improved by direct parameter changes in NSN RAN

Cap. Mngmt Capacity Bottlenecks & AnalysisRAN capacity management includes three sequential steps:Common Channel Load Monitoring- RACH, FACH, SCCPCH & PCH Load1.Counter & KPI monitoring with agreed trigger thresholds (daily/weekly) to measure resource usage or/and blocking.Air Interface Load Monitoring2.Detailed Blocking cause analysis & optimisation actionsR99 Usage3.Possible Hardware Capacity upgrade actions & verifications UL capacity issuesCapacity upgrade process involves making a decision as to whether an upgrade is required or whether the network is likely to benefit from further optimisation. HSDPA DL power & UsageIf an upgrade is required, upgrade verification is performed once the upgrade has been implemented DL Code UsageNumber of HSPA UsersBTS Capacity monitoringSmart phones Overall Flowchart for Capacity ManagementRU20 Reporting Suite Capacity ReportsRU20 full report set contains following capacity reports CCH Load includes:RSRAN068 RNC CapacityRACH pre-amble RSRAN085 RNC Capacity UsageRACH-c and RACH-u load RSRAN066 Node B CapacityFACH-c and FACH-u loadRSRAN067 Cell CapacityPCH loadRSRAN068 Iub CapacitySCCPCH power load RSRAN086 Cell PowerRSRAN097 NRT DCH Allocations StatisticsCCH load of each cell needs to be measured, for example FACH-c, FACH-u and PCCH transport channels can be multiplexed into same SCCPCHRSRAN013 NRT Radio Bearer Statistic

The PRACH preamble load depends upon the no. of UE making use of RACH transport channel. RACH transport channel may be used for the transfer of either user plane (RACH-u) or control plane (RACH-c) information. PRACH load can be reduced by:Increasing the number of available PRACH preamble signaturesIncreasing the number of available PRACH access slotsIncreasing the number of available PRACHCheck whether a large amount of signalling generated by cell, URA, location area or routing area updates. If so, consider adjusting the area boundaries. Evaluate whether or not there is excessive user plane data transfer within CELL_FACH. If so, consider reducing the RLC buffer thresholds that trigger the transition to CELL_DCHUpgrading the BTS configuration in terms of an additional carrierTotal no. of RACH Frames=RRIndPeriod/Length of 1 RACH Framei.e. 200ms/20ms=10M1000C176SUM_RACH_ACK_PREAMBLESM1000C177DENOM_RACH_ACK_PREAMBLES RACHCapacity parameter- HW capacity reserved for a RACH transport channel in the BTS.RACH Capacity is indicated as the capacity of BTS to decode RACH messages in a 10 ms radio framealso Defines the number of PRACH preamble signatures used Range 1,2,3,4 (messages) and default = 2Recemmended value:4For example if the RACHCapacity = 2 (default) then it means that the BTS can decode 2 RACH messages in every 10ms radio frame

S-CCPCH Configuration 1S-CCPCH Configuration 2 In this configuration, PCH Bit Rate is limited to PCH bit rate to 8 kbpsPCH24kbpsEnabled is configured to enabled with this configuration PCH is multiplexed with the FACH-u and FACH-c PCH bit rate is increased to 24 kbpsPCH always has priorityPCH is allocated its own separate S-CCPCH SF64 is required to transfer the FACH-u and FACH-c bit ratesSF128 is allocated to the PCH to support the increased bit rateRAS06 and RU10 support a PCH bitrate of 8 KbpsRU20 support PCH bitrate of 8kbps and 24 kbps Transport block size of 80 bits & carry a single paging record per TTI (10 ms TTI)Transport block size of 240 bits & 10 ms TTI i.e. single paging record can be broadcasted per 10 ms TTI24kbps paging channel require activation of second SCCPCH channelFACH-c and FACH-u load=100 paging records per second PCH load=a single cell can thus page maximum 100 UEs per secondMax PCH Throughput 8 kbps max 100 Pages/s per cell 24Kbps paging Channel - Impact to Code and power capacityHSDPA cannot use 15 HS-PDSCH codes when HSUPA 2 ms TTI is enabled with 24 kbps PCH(B/coz Channelisation code for 24 kbps PCH uses a larger section of the code tree)The transmit power of the S-CCPCH is defined using the parameters:PtxSCCPCH1 (PCH/FACH or only FACH) PtxSCCPCH2 (Standalone PCH)PtxSCCPCH3 (S-CCPCH for SAB) PtxSCCPCH2SF128 (Standalone PCH SF128 / 24kbps)The PtxSCCPCH2SF128 parameter defines the transmit power of the S-CCPCH used to transfer the 24 kbps PCHAll parameters define the transmit power of the data bits (rather than the transmit power of the TFCI and Pilot bits) SCCPCH load is used by PS in downlink channel type selection algorithm Average SCCPCH load-- ratio between the SCCPCH transmission power and the CPICH power. incremented when the MAC-c sends to the RRM an internal message (every 20 seconds, including 0.5s sampling period) with the common channel information

The load of different transport channels (FACH-u, FACH-c and PCH) can be monitored separatelyRNC_2029b FACH-u Load RNC_2030b FACH-c Load

Paging Types and PCH LoadRAS06 and RU10 support a PCH bitrate of 8 KbpsWhen the network needs to contact a certain user a Paging procedure will take place. Transport block size of 80 bits & carry a single paging record per TTI (10 ms TTI)Paging method used depends on RRC state of UE: i.e. single paging record can be broadcasted per 10 ms TTIIDLE: Paging Type 1 - over PCH - LA/RA level - CN originated=100 paging records per second Cell/URA-PCH: Paging Type 1 - over PCH - Cell/URA level - CN/RNC origin.=a single cell can thus page maximum 100 UEs per secondCell-DCH/Cell-FACH: Paging Type 2 / over SRB / Cell level Max PCH Throughput 8 kbps max 100 Pages/sec per cell In case of too high Paging Load a considerable percentage of paging messages could get lost causing a bad user experience (non-reachability of UEs due to missing pages).e.g. high traffic, LAC oversize,). From S-CCPCH Configuration 1, we know that S-CCPCH can be shared with the FACH-c and FACH-u but PCH always has priority. It means that high Paging load has an impact upon FACH capacity when single S-CCPCH is configured.Example:The average PCH Throughput approaches 7kbps several times per day It is a clear symptom of PCH congestion during the traffic peak hour.Average PCH Load equal to 80..90% at RNCLAC levelIt is a highly congested situation, a high rate of missing pages is expected and LAC splitting needs to be planned. The Paging success rate starts to decrease when PCH throughput exceeds 4-4.5kbps, that is a PCH Load of 50-55% approximately and is below 90% when PCH throughput exceeds 6kbpsThreshold of 50% PCH Load confirmed as Rule of Thumb to trigger PCH Load optimization Paging Load Optimization: LAC splittingEnabling a 2nd S-CCPCH without 24 kbps paging channel will not increase the PCH capacity (8kbps), but only FACH capacity.LAC splitting is needed to reduce the Paging LoadPaging Load Optimization: DRX Cycle LengthDRX Cycle Length changed from 1280ms to 640msLinear region increased from 45% to 58%Paging Load Optimization: (RU20) 24 kbps Paging Channel24 kbps Paging Channel feature can increase the paging channel capacity three times higher from the 8 kbps RU20 support PCH bitrate of 8kbps and 24 kbpsSo PCH throughput is increased- 24 kbps PCHTransport block size of 240 bits & 10 ms TTI=Up to 8 paging records per TTI allowed (3GPP) When the amount of paging messages exceeds 50% of the nominal capacity, its good time to start thinking about actions to reduce paging channel load to avoid degradation in paging success rate.If 1 paging record broadcasted/10ms TTI=100 paging records per second= 1 single cell can page 100 UEs/sec50 msg/sec for 8 kbps PCH Then for 8 paging records/10ms TTI=1 single cell can page 8*100=800 UEs/sec250 msg/sec for 24 kbps PCH Max PCH Throughput 24 kbps max 800 Pages/sec per cell Example: Updating 8 kbps to 24 kbps PCHObject Parameter Name Abbreviated Name Actual value new valueRNC Low utilization time to trigger of the MAC-d flow MACdflowutilTimetoTrigger 2 sec 0 sec * RNC Window size of the MAC-d flow throughput measurement MACdflowthroughputAveWin 3 sec 2 sec RNC Low throughput time to trigger of the E-DCH MAC-d flow EDCHMACdFlowThroughputTimetoTrigger 5 sec 1 sec RNC Window size of E-DCH MAC-d flow throughput measurement EDCHMACdFlowThroughputAveWin 3 sec 2 sec RNC Uplink traffic volume measurement low threshold TrafVolThresholdULLow128 bytes 256 bytes RNC UL/DL activation timer UL_DL_activation_timer 2 sec 1 sec RNC Inactivity timer for uplink 8kbps DCH InactivityTimerUplinkDCH8 5 sec 2 sec RNC Inactivity timer for uplink 16kbps DCH InactivityTimerUplinkDCH16 5 sec 2 sec RNC Inactivity timer for uplink 32kbps DCH InactivityTimerUplinkDCH32 5 sec 2 sec PCH loading and FACH throughputOne SCCPCH and 8 kbps PCH CaseWhen SCCPCH is heavily loaded there is risk that FACH messages are delayed or even dropped. This may cause reconfiguration process failures and PS RABs drops.Paging Parameter Recommendations 3GParameter Name (Cell level)Def/CurrentRecommendedN30032T3002000ms2000ms (10)Parameter Name (RNC level)CurrentRecommendedWaitTimeRRCconversational 32WaitTimeRRCstreaming 32WaitTimeRRCinteractive 58WaitTimeRRCbackground 58WaitTimeRRCsubscribed 33WaitTimeRRCemergency 11WaitTimeRRCinterRATreselectio33WaitTimeRRCregistration 55WaitTimeRRChighPrioritySignalling 12WaitTimeRRClowPrioritySignalling 52WaitTimeRRCunknown 12WaitTimeRRCother 02

Air/Radio Interface Load/Capacity Monitoring-- (R99 Usage, UL Capacity Issues, Radio interface monitoring includes resources that cause Admission control to reject establishment of new Connection/bearerUL PowerDL PowerDL CodesNo. of HSPA users When HSPA is enabled in the cell, the DL and UL resources are shared between HSPA and R99 usersBoth R99 and HSPA should be monitoredReactive Measurements Setup Failures due ACRRC/RAB setup failuresPS Call setup failures due AC HSDPA setup failures Setup failures due UL DCHMax. Number of HSDPA users reachedRejection rates in downlink and uplink SRB, AMR, CS data, PS data, separately for UL and DLLow HSDPA throughputChannelisation code blocking rate Proactive Measurements Common channel Load (RACH, FACH, PCH)R99 Usage - Overview of cell loading status in UL/DL for R99 traffic onlyHSPA throughput limitationsHSPA Power & UsageChannelisation Code utilisationSimultaneous number of HSDPA usersR99 Usage:

UL Capacity Issues:UL admission control start blocking incoming traffic if the RTWP (Received Total Wideband Power) and controlled part of UL noise increase too muchFor years this has been solved by increasing the targets of the AC but now in 3G 1 UE transmission interferes the other UEsOne problematic connection can make the other UEs increasing the tx power and the cell starts breathingthe coverage decreases as the UEs in the cell edge run out of tx powerThe control must be returned to 3G network by decreasing the AC targets and blocking the traffic in a controlled waySystem NoiseSystem noise (WCEL: PrxNoise) is the sum of all stationary noises;thermal noiseinterference caused by spurious emissions of other systems,noise caused by additional equipment such as repeatersPrxNoise can vary place to place and even time to timePrxNoise is a RNP parameter whose setting affects the capacity of cellPrxNoise too low: overestimation of cell load and can lead to unnecessary call blockingPrxNoise too high: underestimation of cell load and can lead to overload situationWrong Prx Noise level causes error to estimated power in PIE (Power Increase Estimation) and PDE (Power Decrease Estimation) algorithms, in turn causes power spiking in the uplink spectrum. Autotuning Prx noise:PrxNoise is updated by the autotuning algorithm which adjust Prx Noise level automatically. Enabled with PrxNoiseAutotuning (WCEL)PrxNoise autotuning step sizes is limited by PrxNoiseMaxTuneAbsolute parameter (by default not limited)Recommended parameter value is 2 dB. Value 2 dB allows 4 dB range in Prx Noise autotuning functionality. In this case PrxNoise should have default value -105 dBm. It is important to verify that prxnoise in the unloaded cell is close to -105 dBm. If that is not the case the cell needs further investigation.PrxTarget is defined relative to PrxNoise.M1000C12 Maximum PrxNoise LevelM1000C13 Minimum PrxNoise LevelPrxTarget is scheduling target for RT services and also NRT service [when there is not E-DCH connections with the cell] Uplink SchedulingPrx_Target_PS is used for NRT scheduling when one or more E-DCH connections have been established. This can be adjusted between PrxTargetPSMax and PrxTargetPSMin. PrxMaxTargetBTS is BTS scheduling target for HSUPA. It is suggested to configure this parameter to be greater than PrxTarget + PrxOffset because the Node B is more responsive than the RNC. NRT PS R99 packet scheduling should be done with target lower than PrxMaxTargetBTS in order to provide capacity for HSUPA usersPrxNoise autotuning should be limitedNote: Requires WCEL level check of minimum PrxNoise

Object Parameter Default Recommended WCELPrxMaxTargetBTS 6 dB6 - 12 dBWCELPrxTarget4 dB4 - 8 dBWCELPrxTargetPSMin 4 dB4 - 8 dBWCELPrxTargetPSMax 4 dB4 - 8 dBRNCPrxNoiseMaxTuneAbsolute not lim 2 dB

Only Paging Type 1 affects the PCH Load

TMO Optimization

1.1.1.1.1. Accessibility Analysis (CS/PS/HS)CS/PS Access Failure Optimization:Call Setup analysis

HSDPA Access Failure Optimization:HSUPA Access Failure Optimization:

1.1.1.1.1. Retainibility Analysis (CS/PS/HS)Voice Drop Call Optimization:1. Monitor Daily Performance Reports/KPIs Worksheet---Pick Worst Offenders2. Identify DCR top offenders. few cells?. Any particular area ? Known Coverage issue? Need a new site ?3. Was the availability of the site 100%?4. Any current alarms on the site / sector?5. Check the alarm history especially for transmission issues (NBAP link failures/T1 fluctuations?)6. Check if the sector is dropping the calls due to RF (Counter: Voice_Drops_due_to_radio_int)7. If not RF, check if the following counters are pegged: Voice Drops due to Iu Voice Drops due to BTS Voice Drops due to Iur (Not applicable for Cleveland or Columbus now) Voice Drops due to RNC Voice Drops due to UE7. If drops are due to RF (Voice Drops due to radio int), check the Site location, Neighbors, Cell to cell HO statistics, PRACH delay distance and Ec/No quality distribution statistics8. Need Tilt / Azimuth change to improve the area? 9. HO issue? All Neighbor Exists? SHO.ISHOIFHO.?? Neighbor Adds?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?R99 PS Drop Call Optimization:HSDPA Drop Optimization:

2.8.1.2.3 Throughput Optimization:HSDPA Throughput Optimization:2.8.1.2.4. Capacity Analysis (Power, Codes, Node-B CE, RNC)

2.8.1.3 UMTS Special Feature Optimization 2.8.1.3.1 Multi Band Load Balancing(MBLB)Candidates for MBLB are Inter Frequency neighbors on different freq layer, if prioritized higher than the source cell layer or neighbors in different bands supported by UE The complete MBLB feature basically consists of following three operations: Triggering Events Target Layer Selection Criteria Handover Execution1.Four Triggering Events: Radio Bearer Setup, Inactivity in Cell-DCH, State Transition to Cell-DCH, Mobility.2.Four Target Layer Selection Criterion: Freq Layer Preference (based on UE capability, Requested Service, Speed etc), Band Preference, Better Coverage, Traffic/Load Balancing.3.IFHO Execution: Blind HO (W/o Comp Mode)- (RB Setup Triggered & Transition to DCH state Triggered); Measurement Based HO(With CM) -( Inactivity Timer Triggered & Mobility Triggered).Layer Priority:IFHO types:Trigger Events:Optimization Strategy:Confirmation to the recommended parameter set in most cases. Some market/Cluster/Site specific adjustments needed in order to meet performance KPI and balance traffic between PCS and AWS bands or between multiple carriers within a specific band.Main Parameters to keep Track /Tune and Effects:1. MBLBRABSetupEnabled; MBLBInactivityEnabled; MBLBStateTransEnabled; MBLBMobilityEnabled(Each type can be enabled on cell level independently on others, by corresponding source cell WCEL parameter (enabling in target cell not needed)2. Preferred Frequency Layer Identifiers: (Parameters used to create/define the preferred network layer for each UE capability / service type combination) Up to 8 preferred frequencies can be listed for each 16 capability & service combination .Example: RNC-1 / PFLIdentifier-1 LaySelWeightLoad=50 LaySelWeightRSCP=0 LaySelWeightPrefLayer= 100 LaySelWeightBand= 0 LowLoadPreference = 1 PreflayerHSDPAxxx=F4 PrefayerR99xxx=F3 PrefayerDCHSCxxx=F1, F2 PreferBandForLayering=F1,3. RSCP thresholds used to make upper or lower frequency bands appear more attractive:BlindHORSCPThrAbove ; BlindHORSCPThrBelow.4. Weights allocated to each component of the Preference Score calculationLaySelWeightPrefLayer; LaySelWeightBand; LaySelWeightRSCP; LaySelWeightLoad5. Whether or not increased weight is given to low loaded cells: LaySelLowLoadPref6. Preferred layers for fast moving UE: PFLFastMovUECS , PFLFastMovUEPS

2.8.2.2. GSM Optimization Process using OSS KPI/Counters2.8.2.2..1. Voice Accessibility Analysis (SDCCH/TCH)2.8.2.2.2. Drop Call Analysis (TCH)

GSM Voice Access Failure Analysis Process GSM Voice Call Analysis Process 2.8.2.2.3 HO Failure Analysis

1.1.1.1.1. Link Imbalance Analysis:Use Link Imbalance Report from KPI reports (DL-UL). It is useful to check if both DL and UL are balanced.IDD/4UD features for DL/UL coverage improvement etc.

1.1.1.2. GSM Special Feature Optimization

IDD, 4UD, MHAIDD combined with MHA and 4UD gives best results according the drive test and OSS data. The MHA and 4UD can improve the performance on highly unbalanced cells (UL limited) and improve coverage in DL with IDD.

IDD, MHAIDD combined with MHA gives also good results but if the cell is highly unbalanced (UL limited) it could not compensate DL totally (cell will be still UL limited). So this configuration is recommended if the cell is 3-5 dB UL limited.

IDD, 4UDIDD improves DL more compared to 4UD on UL. This configuration is recommended if the cell is 1-3 dB UL limited (the gain of 4UD is less in rulal).

Expected Results:Drive test Bigger coverage area (2-3 dB more in rural, better indoor, better overlapping in HO) Better average RxQual (25 % better) Less HO attempts (25 % less) and Cell re-selections (24 % less) Better (E)GPRS data rate OSS data More traffic (31%) Better DCR (0.26%) Less HO attempts (~23%)

GSM Voice Call Handover Analysis Process

IDD (intelligent DL Diversity)Downlink diversity means that downlink signal is sent via two separate transceivers, which are fed to separate antennas. IDD method provides its best gain in low-correlated channels. Therefore, phase hopping is used to change phasing between adjacent burst, which decreases correlation between the main and auxiliary transmitter. Both transmitters transmit on the same frequency, but the transmission of secondary transmitter is randomly delayed to decrease correlation between the main and secondary transmitters. Phase hopping could increase interference levels.Intelligent downlink diversity (IDD) doesnt need to be enabled from BSC. It requires re-commissioning of the BTS. During the commissioning with BTS manager software the IDD option needs to be switched on. From network side only the master TRX will be seen, the auxiliary TRX will not be seen by BSC. 4XUD (Four way UL Diversity)Four Way Uplink Diversity means that four received signals are combined together by using several combining techniques (Interference Rejection Combining (IRC), Maximum Ratio Combining (MRC), to get a unique combined signal with better quality.IRC eliminates correlated noise received by both antennas. If no correlated noise exists, IRC behaves like a normal Maximum Ratio Combiner allowing traffic to flow without requiring noise reduction. The combining gain depends on Dominant Interference Ratio and angular spread of Interference Post Detection Maximum Ratio.Regarding 4UD activation, The 4UD (as well as the IDD) is activated using the BTS manager software during the BTS commissioning. During the commissioning the 4UD feature needs to be switched on. The 4UD can only be switched on if the IDD option has been switched on earlier, so 4UD cannot be used without IDD.For activating the 4UD feature, in the BSC, the Rx DIV parameter needs to be set to Yes (Y) in order to be able to activate 4UD.SHO overhead RT = 130-199SHO overhead NRT = 30-45Poor RAB drop for PS, HSDPA and HSUPA observed for Node B's on ATMPoor RAB drop rate observed for some sites working on ATM and when the BTS commissioning for these sites were audited it was found that the problem was with the bit rate definition for RT and NRT services.For signaling and RT services-- the bit rate should be "CBR" (constant bit rate) and for NRT services-- it has to be "UBR+" (unspecified bit rate). Initially poor performing sites were identified and rectified accordingly and then all ATM sites were audited for commissioning recheck.

100% HS AFRThe software version was not compatiable with 4 way UL Rx Diversity enabled due to the software glitch, temporary solution untill next software loadUntil new version comes:WCEL - HSUPA2msTTIenabled changed from Enabled(1) to Disabled 0WCEL - MaxTotalUplinkSymbolRate Changed from 3(5760kbps) to 2(3840 kbps)

Poor ISHO success rate observed for RTIn the compressed mode it is not able to decode the BCCH BSIC or is not able to make accurate decision.GsmMaxMeasPeriod parameter tuned from 3 Secs to 6 Secs so that the probability to decode BCCH BSIC of the GSM sites can be increasedThe value of GsmMaxMeasPeriod must be greater than the value of GsmNcellSearchPeriod. The value for this parameter was changed from 6 to 12 value

FMCx,HOPxFMCXCore PCSBoundaryCoreFMCGParameterRTNRTHSDPAHSDPA MultiRTNRTHSDPAHSDPA MultiRTNRTHSDPAHSDPA MultiDL DPCH Transmission power Cancellation Offset (db)-3DL DPCH Tx Power threshold for AMR (db)-3DL DPCH Tx Power threshold for CS (db)-3DL DPCH Tx Power threshold for NRT PS (db)-1DL DPCH Tx Power threshold for RT PS (db)-3GSM HO cause by CPICH EcNo1- Enabled0- Disabled0- Disabled1- Enabled1- Enabled1- Enabled1- Enabled1- Enabled1- Enabled0-Disabled0-Disabled1- EnabledGSM HO cause by CPICH RSCP1- Enabled0-Disabled1- Enabled0-Disabled0-DisabledGSM HO cause by DL DPCH TX Power0- DisabledGSM HO cause by UE TX Power1- EnabledGSM HO cause by UL DCH Quality0- DisabledGSM Neighbor Cell Search Period (MEasRep)0IMSI Based GSM HO0- Not AllowedISHO Cancellation cause by CPICH EcNo1- EnabledISHO Cancellation cause by CPICH RSCP1- EnabledISHO Cancellation cause by DL DPCH TX Power1- DisabledISHO Cancellation cause by UE TX Power1- EnabledMaximum BSIC Identification Time (s)0- Feature not Used0- Feature not Used0- Feature not Used0- Feature not Used0- Feature not Used220- Feature not Used0- Feature not Used220- Feature not UsedMaximum Measurement Period (MeasRep)6Maximum Averaging Window (MeasRep)6Measurement reporting Interval2- 0.5sMaximum Interval between Hos (s)10Maximum Interval between Repetitive inter_RAT SLHOs (s)30Minimum measurement Interval (s)2NameUE TX Power Filter Coefficient8- Approx. 10msUE Tx Power threshold for AMR (db)-3UE Tx Power threshold for CS (db)-3UE Tx Power threshold for NRT PS (db)-1UE Tx Power threshold for RT PS (db)-3UE Tx Power Time Hysteresis13- 1280msUsage of Directed Retry of AMR call Inter-System Handov0- DisabledCore PCSBoundaryCoreCore_NRT SHOOverhead ReductionBoundary_NRT SHOOverhead ReductionFMCSParameterRTNRTHSDPAHSDPA MultiRTNRTHSDPAHSDPA MultiRTNRTHSDPAHSDPA MultiRTNRTHSDPAHSDPA MultiRTNRTHSDPAHSDPA MultiActive Set Weighting coefficient0Addition Reporting Interval2- 0.5sAddition Time11- 320ms12- 640ms12- 640msAddition Window (db)331.533303330322Allow E-DCH usage EcNo offset (db)0change originCPICH Ec/No filter Coefficient3- Apprx. 600msCPICH Ec/No HHO Cancellation (db)-17-17-17-17-11-14-14-11-17-17-17-17-17-14CPICH Ec/No HHO Cancellation Time13- 1280msCPICH Ec/No HHO Threshold (db)-19-19-19-19-13-16-16-13-19-19-19-19-19-16CPICH Ec/No HHO Time Hysteresis13- 1280ms11- 320ms11- 320ms13- 1280ms13- 1280ms13- 1280ms13- 1280ms13- 1280ms13- 1280ms11- 320ms11- 320ms13- 1280ms11- 320ms13- 1280msCPICH EcNo offset E-DCH usage Removal (db)2CPICH RSCP HHO Cancellation (db)-102-102-102-102-109-112-112-109-112-112-112-112-112-112CPICH RSCP HHO Cancellation Time13- 1280msCPICH RSCP filter Coefficient3- Apprx. 600msCPICH RSCP HHO Threshold (db)-105-105-105-105-112-115-115-112-115-115-115-115-115-115CPICH RSCP HHO Time Hysteresis11- 320ms11- 320ms11- 320ms11- 320ms12- 640ms12- 640ms13- 1280ms12- 640ms11- 320ms11- 320ms11- 320ms11- 320ms11- 320ms11- 320msDetected Set reporting Based HHO2- EnabledDrop Reporting Interval0- No periodical reporting2- 0.5s2- 0.5s2- 0.5s0- No periodical reporting2- 0.5s2- 0.5s2- 0.5s0- No periodical reporting2- 0.5s2- 0.5s2- 0.5s2- 0.5s2- 0.5sDrop Time12- 640ms12- 640ms12- 640ms12- 640ms12- 640ms12- 640ms13- 1280ms12- 640ms12- 640ms12- 640ms13- 1280ms12- 640ms12- 640ms12- 640msDrop Window (db)663.566666666644IMSI Based SHO0- Not AllowedMaximum Active Set Size3NameReplacement Reporting Interval2- 0.5sReplacement Time12- 640ms11- 320ms11- 320ms11- 320ms12- 640ms11- 320ms13- 1280ms11- 320ms12- 640ms11- 320ms13- 1280ms11- 320ms11- 320ms11- 320msReplacement Window (db)62.51.52.562.532.562.532.522

Core PCSBoundaryCoreFMCIParameterRTNRTHSDPAHSDPA MultiRTNRTHSDPAHSDPA MultiRTNRTHSDPAHSDPA MultiDL DPCH Tx Power threshold for AMR (db)-1DL DPCH Tx Power threshold for CS (db)-3DL DPCH Tx Power threshold for NRT PS (db)-1DL DPCH Tx Power threshold for RT PS (db)-3IFHO cause by CPICH EcNo1- EnabledIFHO cause by CPICH RSCP1- EnabledIFHO cause by DL DPCH TX Power0- DisabledIFHO cause by UE TX Power0- Disabled0- Disabled0- Disabled0- Disabled1- Enabled1- Enabled1- Enabled1- Enabled0- Disabled0- Disabled0- Disabled0- DisabledIFHO cause by UL DCH Quality0- DisabledIMSI Based IFHO0- Not AllowedMaximum Measurement Period (MeasRep)6MBLB due to Mobility EcNo offset (db)2MBLB due to Mobility RAB Combinations0- AllMaximum Averaging Window (MeasRep)6Measurement reporting Interval2- 0.5sMaximum Interval between Hos (s)10Maximum Interval between Repetitive IF SLHOs (s)30Minimum measurement Interval (s)2NameNeighbour cell Search Period (MeasRep)0UE TX Power Filter Coefficient8- Approx. 10msUE Tx Power threshold for AMR (db)-3UE Tx Power threshold for CS (db)-3UE Tx Power threshold for NRT PS (db)-1UE Tx Power threshold for RT PS (db)-3UE Tx Power Time Hysteresis13- 1280ms

Dual Cell SettingsParameterValue

DCellHSDPAEnabledEnabledHSDPA64QAMallowedEnabledMaxTotalUplinkSymbolRate5760HSPDSCHCodeSet54560HSUPA2MSTTIEnabledEnabledDLmaxBitRateSF161080 kbpsAMRLCRelatTXWindowRate7Size512AMRLCRelatTXWindowRate8Size750MaxBitRateNRTMacdflow0MaxNbrOfHSSCCHCodes4WCEL_ACHSPDSCHMarginSF1282WCEL_ACDPCHOverHSPDSCHThreshold5WCEL_ACHSPA72UsersEnabledEnabledWCEL_ACHSDPA14MbpsPerUserEnabledwbtsDCellHSDPACapaHODisabledhcFDPCHEnabledDisabledACDCellHSDPAFmcsIdERROR:#NAME?FRLCEnabledEnabledRNFC

Power settingsWCELACACLCLCPSPSPSWCELACService AffectingNon-Service AffectingCell DL PowerMaxDLPowerCapabilityPtxCellMaxPtxMaxHSDPAPtxTargetPtxOffsetPtxTargetPSMaxPtxTargetPSMinPtxHighHSDPAPwrPtxPrimaryCPICHPtxTargetHSDPA20W430430430425542036042533042040W460460460455545039045535445060W478478478473546840847335446830W4484484484435438378443354438

RNC ParamatersDUMP :6/5/14 1:52

RNC databaseTotalTRUEFALSERNC10100RNAC10100RNFC1091RNHSPA10010RNMOBI1037RNPS1073RNRLC10100RNTRM1082WRAB251015WBTS293702937WCEL1394967287221WCEL power13949340410545WCEL_AC13949119791850WCEL_AC power1394951678662WCEL_HC common13949243911510WCEL_HC MBLB91741689006WCEL_HC LTE840884080WCEL_LC136732760WCEL_LC power1395251778652WCEL_PC887150780WCEL_PS125647870WCEL_PS power1395221483838WCEL_SIB common622577240WCEL_SIB MBLB761915554775WCEL_SIB LTE410443045541

Sheet2CLASSParametersdefaultCelcomDeviationRemarksModificationRNC TEMPLATERNACRNACId11TRUECell DL Power20W30W40W60WRNACAMRLoadTxPower11TRUEwcelMaxDLPowerCapability4304484604781 rf 9001rf 2100 2rf+2hs 2100 3rf+3hs 2100POWER (W)LTE Interworking with 3GMBLBRNACAMRNumofReconf1010TRUEwcelPtxCellMax430448460478CLASSParametersdefaultCelcomDeviationRemarksModificationcarrier 1carrier 1carrier 1carrier 2carrier 1carrier 2carrier 320304060107621071210737U9RNACAMRwinSizeSCload1010TRUEwcelPtxMaxHSDPA430448460478WCELAdminCellState01FALSECell lock/unlock status.RNACAdjustmentPeriod22TRUEwcelPtxTarget425443455473WCELCSGroupId00TRUE000000000000RNACAdjustmentRatio00TRUEwcelPtxOffset5555WCELCTCHCapaHighPri00TRUE000000000000RNACBitRateSetPSNRT00TRUEwcelPtxTargetPSMax420438450468WCELCUCEcNoThreshold3131TRUE313131313131313131313131RNACDCHSlopeOfTheCurve22TRUEwcelPtxTargetPSMin360378390408WCELCUCRSCPThreshold-92-92TRUE-92-92-92-92-92-92-92-92-92-92-92-92RNACDLInLoopPCStepSizeCPC22TRUEwcelPtxHighHSDPAPwr425443455473WCELEVAMCapability10FALSEno value000000000000RNACDLLoadSource22TRUEwcelPtxPrimaryCPICH330354354354WCELMultiplePLMNListIncluded00TRUE000000000000RNACDLmaxBitRateSF1287575TRUEwcelPtxTargetHSDPA420438450468WCELPCH24kbpsEnabled01FALSE24 kbps paging channel feature enabled111111111111RNACDLmaxBitRateSF16600600TRUEWCELPRACHDelayRange33TRUE333333333333RNACDLmaxBitRateSF2563535TRUEWCELPSGroupId00TRUE000000000000RNACDLmaxBitRateSF32309309TRUEWCELPWSMAVLimitDCHSDPA1010TRUE101010101010101010101010RNACDLmaxBitRateSF64133133TRUEWCELPWSMAVLimitNRTHSDPA1010TRUE101010101010101010101010RNACDLpuncturingLimit57FALSEokWCELPWSMAVLimitRTDCH3737TRUE373737373737373737373737RNACDownlinkInnerLoopPCStepSize11TRUEWCELPWSMAVLimitRTHSDPA00TRUE000000000000RNACEDCHSlopeOfTheCurve2020TRUEWCELPWSMAVPwrNRTHSDPA3131TRUE313131313131313131313131RNACExpectReorderingPDCP00TRUEWCELPWSMAVPwrRTHSDPA3737TRUE373737373737373737373737RNACFmaxPeriodPDCP256256TRUEWCELPWSMCellGroup00TRUE000000000000RNACFmaxTimePDCP55TRUEWCELPWSMEXPwrLimit3737TRUE373737373737373737373737RNACFreePtxSafetyMarginStr00TRUEWCELPWSMEXUsrLimit55TRUE555555555555RNACPrachBetaC1201010TRUEWCELPWSMSDLimitDCHSDPA55TRUE555555555555RNACPrachBetaC151313TRUEWCELPWSMSDLimitNRTDCH1010TRUE101010101010101010101010RNACPrachBetaC301212TRUEWCELPWSMSDLimitNRTHSDPA55TRUE555555555555RNACPrachBetaC601111TRUEWCELPWSMSDLimitRTDCH1010TRUE101010101010101010101010RNACPrachBetaD1201515TRUEWCELPWSMSDLimitRTHSDPA55TRUE555555555555RNACPrachBetaD151515TRUEWCELPWSMSDPwrNRTHSDPA3434TRUE343434343434343434343434RNACPrachBetaD301515TRUEWCELPWSMSDPwrRTDCH3737TRUE373737373737373737373737RNACPrachBetaD601515TRUEWCELPWSMSDPwrRTHSDPA3434TRUE343434343434343434343434RNACHSFACHDiscardTimer20FALSERelated to HS Cell FACH feature which is not active.WCELPWSMShutdownOrder00TRUE000000000000RNACHSFACHResetTimer20FALSERelated to HS Cell FACH feature which is not active.WCELPWSMShutdownRemCell00TRUE000000000000RNACHeaderCompressionMethod00TRUEWCELPowerSaveHSPAType00TRUE000000000000RNACICRHostOperatorId2550FALSEWCELPtxPrimaryCPICH330354FALSEcell specific value based on Optimization and Power Capability.YesRefer to worksheet " summary configuration"330354354354RNACLoadBasedAMRCodecMode00TRUEWCELRACHCapacity22TRUE222222222222RNACMaxAdjustmentStep88TRUEWCELRNARGroupId00TRUE000000000000RNACMaxFreezingTime3030TRUEWCELRRCconnRepTimer166TRUE666666666666RNACMaxHeaderPDCP168168TRUEWCELRRCconnRepTimer255TRUE555555555555RNACMaxNumberOfReAttemptsCong22TRUEWCELRelocComm_in_InterRNC_HHO00TRUE000000000000RNACMinPrefChange33TRUEWCELSACB00TRUE000000000000RNACNonTCPspacePDCP1515TRUEWCELShutdownStepAmount1010TRUE101010101010101010101010RNACPCPreamble00TRUEWCELShutdownWindow1515TRUE151515151515151515151515RNACPCrangeDL1522FALSEokWCELToAWE_CCH1010TRUE101010101010101010101010RNACPeriodULRCAMR25510FALSEokWCELToAWS_CCH2525TRUE252525252525252525252525RNACPrefSubtract22TRUEWCELUTRAN_DRX_length55TRUE555555555555RNACPrxNoiseMaxTuneAbsolute2554FALSERNC 127 using defaultYes 127WCELWCELCSCNId655351FALSEok111111111111RNACSRBDelay77TRUEWCELWCELPSCNId655352FALSEok222222222222RNACSignallingLinkInactivityTimer44TRUEWCELWCelState00TRUE000000000000RNACStepSizeForDCHBLER3030TRUEWCELNumofEagch11TRUE111111111111RNACStepSizeForEDCHBLER33TRUEWCELNumofErgHich11TRUE111111111111RNACTCPspacePDCP1515TRUEWCELcellLevel00TRUE000000000000RNACTDMultForHSDPAStreaming66TRUEWCEL_ACAMROverSC9090TRUE909090909090909090909090RNACTFDCHZeroBitRate1638416384TRUEWCEL_ACAMROverTransmission99TRUE999999999999RNACULmaxBitRateSF1283030TRUEWCEL_ACAMROverTxNC-10-10TRUE-10-10-10-10-10-10-10-10-10-10-10-10RNACULmaxBitRateSF16273273TRUEWCEL_ACAMROverTxNonHSPA00TRUE000000000000RNACULmaxBitRateSF2561515TRUEWCEL_ACAMROverTxTotal2020TRUE202020202020202020202020RNACULmaxBitRateSF32120120TRUEWCEL_ACAMRSF-2-2TRUE-2-2-2-2-2-2-2-2-2-2-2-2RNACULmaxBitRateSF646060TRUEWCEL_ACAMRTargetSC7070TRUE707070707070707070707070RNACULmaxBitRateSF8500500TRUEWCEL_ACAMRTargetTransmission88TRUE888888888888RNACULpuncturingLimit77TRUEWCEL_ACAMRTargetTxNC-20-20TRUE-20-20-20-20-20-20-20-20-20-20-20-20RNACUlScrCodeMin10000001000000TRUEWCEL_ACAMRTargetTxNonHSPA-10-10TRUE-10-10-10-10-10-10-10-10-10-10-10-10RNACUpLinkInitialTransmitPowerMode00TRUEWCEL_ACAMRTargetTxTotal00TRUE000000000000RNACUpLinkRecoveryPeriodPowerMode00TRUEWCEL_ACAMRUnderSC5050TRUE505050505050505050505050RNACWaitTimeRRCbackground58FALSEokWCEL_ACAMRUnderTransmission22TRUE222222222222RNACWaitTimeRRCconversational32FALSEokWCEL_ACAMRUnderTxNC-100-100TRUE-100-100-100-100-100-100-100-100-100-100-100-100RNACWaitTimeRRCemergency11TRUEWCEL_ACAMRUnderTxNonHSPA-100-100TRUE-100-100-100-100-100-100-100-100-100-100-100-100RNACWaitTimeRRChighPrioritySignalling12FALSEokWCEL_ACAMRUnderTxTotal-100-100TRUE-100-100-100-100-100-100-100-100-100-100-100-100RNACWaitTimeRRCinterRATreselection35FALSEokWCEL_ACAdminPICState11TRUE111111111111RNACWaitTimeRRCinteractive58FALSEokWCEL_ACAssignedPICPool00TRUE000000000000RNACWaitTimeRRClowPrioritySignalling52FALSEokWCEL_ACCCHSetupEnabled01FALSECommon channel setup feature enabled.111111111111RNACWaitTimeRRCother02FALSEokWCEL_ACCIRForFDPCH-44-44TRUE-44-44-44-44-44-44-44-44-44-44-44-44RNACWaitTimeRRCregistration15FALSEokWCEL_ACCPICHEcNoSRBMapRRC-16-16TRUE-16-16-16-16-16-16-16-16-16-16-16-16RNACWaitTimeRRCstreaming32FALSEokWCEL_ACCPICHRSCPSRBMapRRC-92-92TRUE-92-92-92-92-92-92-92-92-92-92-92-92RNACWaitTimeRRCsubscribed33TRUEWCEL_ACCPICHtoRefRABoffset20-40FALSECelcom default is -4dBYes-40-40-40-40-40-40-40-40-40-40-40-40RNACWaitTimeRRCunknown12FALSEokWCEL_ACCSAMRModeSET07FALSEok777777777777RNCCommonMCC655350FALSEWCEL_ACCSAMRModeSETWB01FALSEok111111111111RNCCommonMNC655350FALSEWCEL_ACCableLoss3030TRUE303030303030303030303030RNCCommonMNCLength00TRUEWCEL_ACCodeTreeOptTimer36003600TRUE360036003600360036003600360036003600360036003600RNCConnectionRetryCounter1010TRUEWCEL_ACCodeTreeOptimisation11TRUE111111111111RNCDLBLERConfInterval2323TRUEWCEL_ACCodeTreeUsage4040TRUE404040404040404040404040RNCEmergencyCallRedirectTimer600FALSEWCEL_ACDPCHOverHSPDSCHThreshold55TRUE555555555555RNCExtendedULDLactivationTmr00TRUEWCEL_ACDRRCprxMargin00TRUE000000000000RNCLCSSupportForAnchoring00TRUEWCEL_ACDRRCprxOffset-10-10TRUE-10-10-10-10-10-10-10-10-10-10-10-10RNCLCSfunctionality01FALSERNC 127 using defaultYes 127WCEL_ACDRRCptxMargin-5-5TRUE-5-5-5-5-5-5-5-5-5-5-5-5RNCMSActivitySupervision2929TRUEWCEL_ACDRRCptxOffset-30-30TRUE-30-30-30-30-30-30-30-30-30-30-30-30RNCN30277TRUEWCEL_ACEVAMInUse00TRUE000000000000RNCN30422TRUEWCEL_ACEvamDInit00TRUE000000000000RNCN30822TRUEWCEL_ACEvamNumPhaseOffset80FALSEno value000000000000RNCPWSMDuration55TRUEWCEL_ACEvamTKeep43200FALSEno value000000000000RNCPWSMExceededTrafficDur2020TRUEWCEL_ACEvamTSweep2160FALSEno value000000000000RNCPageRep1stInterv77TRUEWCEL_ACFDPCHCodeChangeEnabled66TRUE666666666666RNCPageRep2ndInterv2020TRUEWCEL_ACFDPCHEnabled00TRUE000000000000RNCRANAPprocInitWait1030FALSEokWCEL_ACFDPCHSetup00TRUE000000000000RNCRTservicesForPS22TRUEWCEL_ACHSDPA64QAMallowed01FALSEHSDPA 64 QAM feature enabled.111111111111RNCRestrictionInterval6060TRUEWCEL_ACHSDPA64UsersEnabled01FALSEHSDPA 64 users feature enabled.111111111111RNCSIB11_priority44TRUEWCEL_ACHSDPAenabled01FALSEenabled111111111111RNCSIB12_priority44TRUEWCEL_ACHSFACHEnabled00TRUE000000000000RNCSIB15_priority40FALSEWCEL_ACHSFACHRel7ConSetupEC4581240FALSEno value. Related to HS cell FACH feature.000000000000RNCSIB18_priority44TRUEWCEL_ACHSPA72UsersPerCell01FALSEHSPA 72 users license feature enabled.111111111111RNCSIB19Priority33TRUEWCEL_ACHSPDSCHCodeSet3254560FALSEok545605456054560545605456054560545605456054560545605456054560RNCSIB1_priority22TRUEWCEL_ACHSPDSCHMarginSF12888TRUE888888888888RNCSIB2_priority22TRUEWCEL_ACHSUPA16QAMAllowed00TRUE000000000000RNCSIB3_priority33TRUEWCEL_ACHSUPA2MSTTIEnabled01FALSEHSUPA 2ms TTI feature enabled.111111111111RNCSIB4_priority33TRUEWCEL_ACHSUPAUserLimit16QAM20FALSEno value. Related to HSUPA 16 QAM feature.000000000000RNCSIB5_priority33TRUEWCEL_ACMHA00TRUE000000000000RNCSIB6_priority33TRUEWCEL_ACMaxBitRateDLPSNRT384384TRUE384384384384384384384384384384384384RNCSIB7_priority11TRUEWCEL_ACMaxBitRateULPSNRT384384TRUE384384384384384384384384384384384384RNCSecOMSIpAddress0.0.0.00.0.0.0WCEL_ACMaxCodeReleases4040TRUE404040404040404040404040RNCServingOMS11TRUEWCEL_ACMaxNbrOfHSSCCHCodes14FALSE4 HS SCCH codes being used.Yes444444444444RNCServingOMSAdminSetting00TRUEWCEL_ACPICState11TRUE111111111111RNCServingOMSSwoRequest00TRUEWCEL_ACPrxLoadMarginDCH2040FALSEok404040404040404040404040RNCT3021012FALSEokWCEL_ACPrxLoadMarginMaxDCH00TRUE000000000000RNCT30444TRUEWCEL_ACPrxOffsetWPS80FALSEno value000000000000RNCT30533TRUEWCEL_ACPtxCellMax430460FALSEdepends on power settings. Refer Power settings.YesRefer to worksheet " summary configuration"430478448460RNCT30744TRUEWCEL_ACPtxDLabsMax370370TRUE370370370370370370370370370370370370RNCT30822TRUEWCEL_ACPtxFDPCHMax9090TRUE909090909090909090909090RNCT30988TRUEWCEL_ACPtxFDPCHMin200200TRUE200200200200200200200200200200200200RNCT31422TRUEWCEL_ACPtxMaxHSDPA430460FALSEdepends on power settings. Refer Power settings.YesRefer to worksheet " summary configuration"430478448460RNCT31633TRUEWCEL_ACPtxOffsetExxCH2ms2020TRUE202020202020202020202020RNCT31744TRUEWCEL_ACPtxOffsetExxCHSHO1212TRUE121212121212121212121212RNCToAWE_NRT_DCH_tti10107FALSEokWCEL_ACPtxOffsetFDPCHSHO66TRUE666666666666RNCToAWE_NRT_DCH_tti20107FALSEokWCEL_ACPtxOffsetHSDPA810FALSEok101010101010101010101010RNCToAWE_NRT_DCH_tti401010TRUEWCEL_ACPtxOffsetWPS80FALSEno value000000000000RNCToAWE_RT_DCH_tti101010TRUEWCEL_ACPtxPSstreamAbsMax370370TRUE370370370370370370370370370370370370RNCToAWE_RT_DCH_tti201010TRUEWCEL_ACPtxTargetHSDPA385450FALSEdepends on power settings. Refer Power settings.Refer to worksheet " summary configuration"420468438450RNCToAWE_RT_DCH_tti401010TRUEWCEL_ACPtxTargetTotMax3276732767TRUE327673276732767327673276732767327673276732767327673276732767RNCToAWE_Speech55TRUEWCEL_ACPtxTargetTotMin3276732767TRUE327673276732767327673276732767327673276732767327673276732767RNCToAWS_NRT_DCH_tti102515FALSEokWCEL_ACRefServForCodePower00TRUE000000000000RNCToAWS_NRT_DCH_tti202515FALSEokWCEL_ACRxDivIndicator11TRUE111111111111RNCToAWS_NRT_DCH_tti402525TRUEWCEL_ACSIRDPCCHOffsetEDPCH00TRUE000000000000RNCToAWS_RT_DCH_tti102525TRUEWCEL_ACSRBBitRateRRCSetupEC66559508927FALSEok508927508927508927508927508927508927508927508927508927508927508927508927RNCToAWS_RT_DCH_tti202525TRUEWCEL_ACSRBMapRRCSetupEC457728310272FALSEok310272310272310272310272310272310272310272310272310272310272310272310272RNCToAWS_RT_DCH_tti402525TRUEWCEL_ACTPCCommandERTarget44TRUE444444444444RNCToAWS_Speech1525FALSEokWCEL_ACUEtxPowerMaxDPCH2424TRUE242424242424242424242424RNCTraceLCSHorizAccur300FALSEWCEL_ACUEtxPowerMaxPRACH2121TRUE212121212121212121212121RNCTraceLCSPriority10FALSEWCEL_ACUEtxPowerMaxPRACHConn2121TRUE212121212121212121212121RNCTraceLCSVertAccur700FALSEWCEL_ACUsersPerHSSCCHCode300FALSEno value000000000000RNCTraceLCSWaitPeriod100FALSEWCEL_HCBlindHOEcNoThrTarget-240FALSEok, RACH EcNo measurement not in use.Yes000000000000RNCULBLERConfInterval2323TRUEWCEL_HCBlindHORSCPThrTarget-95-25FALSEokYes-25-25-25-25-25-25-25-25-25-25-25-25RNCUL_DL_activation_timer22TRUEWCEL_HCCellWeightForHSDPALayering100100TRUE10010010010010010010010010010010080RNCUL_DLcapacityReqWait1040FALSEokWCEL_HCDCellHSDPACapaHO00TRUE0000000033374145RNCmaxCallCapabilityBased on license in RNCWCEL_HCDLLoadStateTTT44TRUE444444444444RNCmaxThroughputBased on license in RNCWCEL_HCHSDPAFmcgIdentifier33374145RNFCAMRWithEDCH01FALSEokWCEL_HCHSDPAFmciIdentifier33374145RNFCAMRWithHSDSCH01FALSEokWCEL_HCHSDPAFmcsIdentifier33374145RNFCAutomDLPlanUpdEnabled00TRUEWCEL_HCHSPAFmcsIdentifier33374145RNFCCCCHforCUCallowed11TRUEWCEL_HCDirectedRRCEnabled10FALSEnot enabled as MBLB is there.000000000000RNFCCMmasterSwitch00TRUEWCEL_HCDirectedRRCForHSDPALayerEnabled01FALSEEnabled for HSDPA 111111111111RNFCCUCforPCHtoDCHallowed11TRUEWCEL_HCHHoMaxAllowedBitrateDL3264FALSEokYes646464646464646464646464RNFCCVUserInactInSignConnRel11TRUEWCEL_HCHHoMaxAllowedBitrateUL3264FALSEokYes646464646464646464646464RNFCCapaSmartphoneEnabled01FALSEokWCEL_HCHSCapabilityHONumbUE33TRUE333333333333RNFCDCHBitRateBalancing11TRUEWCEL_HCHSCapabilityHOPeriod50FALSEokYes000000000000RNFCDCHScheOverIur00TRUEWCEL_HCHSDPALayeringCommonChEnabled01FALSEenabled.Yes111111111111RNFCDLOptimisationUsage11TRUEWCEL_HCHSLoadStateHSDBRLimit3232TRUE323232323232323232323232RNFCDynUsageHSDPAReturnChannel01FALSEokWCEL_HCHSLoadStateHSDOffset127127TRUE127127127127127127127127127127127127RNFCEUTRAdetection01FALSEokWCEL_HCHSLoadStateHSUBRLimit2424TRUE242424242424242424242424RNFCEmergencyCallISHOSupport00TRUEWCEL_HCHSLoadStateHSUOffset127127TRUE127127127127127127127127127127127127RNFCEmergencyCallRedirect00TRUEWCEL_HCHSLoadStateHSUResThr22TRUE222222222222RNFCFRLCEnabled01FALSEokWCEL_HCHSPACapaHO00TRUE000000000000RNFCFastDormancyEnabled11TRUEWCEL_HCIncomingLTEISHO01FALSEok, based on LTE coverage nearby.Yes111111111111RNFCFlexUpgrUsage01FALSEokWCEL_HCLHOCapaReqRejRateDL7070TRUE707070707070707070707070RNFCHLSModeSelection00TRUEWCEL_HCLHOCapaReqRejRateUL7070TRUE707070707070707070707070RNFCHSDPA16KBPSReturnChannel01FALSEokWCEL_HCLHODelayOFFCapaReqRejRate3030TRUE303030303030303030303030RNFCHSDPA48UsersEnabled01FALSEokWCEL_HCLHODelayOFFHardBlocking3030TRUE303030303030303030303030RNFCHSDPADynamicResourceAllocation01FALSEokWCEL_HCLHODelayOFFInterference3030TRUE303030303030303030303030RNFCHSDPAMobility01FALSEokWCEL_HCLHODelayOFFResRateSC3030TRUE303030303030303030303030RNFCHSPAInterRNCMobility02FALSEokWCEL_HCLHOHardBlockingBaseLoad1010TRUE101010101010101010101010RNFCHSPAOverIurExt00TRUEWCEL_HCLHOHardBlockingRatio5050TRUE505050505050505050505050RNFCISHOCancellation01FALSEokWCEL_HCLHOHystTimeCapaReqRejRate22TRUE222222222222RNFCISHOInIurMobility00TRUEWCEL_HCLHOHystTimeHardBlocking22TRUE222222222222RNFCIntelligentEmergencyCallISHOSupport00TRUEWCEL_HCLHOHystTimeInterference22TRUE222222222222RNFCIuPSrelWait3G2GMultiServ44TRUEWCEL_HCLHOHystTimeResRateSC22TRUE222222222222RNFCMIBPLMNIdIncluded00TRUEWCEL_HCLHONRTTrafficBaseLoad1010TRUE101010101010101010101010RNFCMOCNenabled00TRUEWCEL_HCLHONumbUEInterFreq00TRUE000000000000RNFCPBSpolicy11TRUEWCEL_HCLHONumbUEInterRAT00TRUE000000000000RNFCPSOpThroUsage015FALSEokWCEL_HCLHOPwrOffsetDL-15-15TRUE-15-15-15-15-15-15-15-15-15-15-15-15RNFCPWSMDriftAllowed00TRUEWCEL_HCLHOPwrOffsetUL-7-7TRUE-7-7-7-7-7-7-7-7-7-7-7-7RNFCPostVerifPeriodDLSynch00TRUEWCEL_HCLHOResRateSC8080TRUE808080808080808080808080RNFCPowerBalancing00TRUEWCEL_HCLHOWinSizeOFFCapaReqRejRate55TRUE555555555555RNFCRABDRAEnabled00TRUEWCEL_HCLHOWinSizeOFFHardBlocking55TRUE555555555555RNFCRRCSetupCCHEnabledR9901FALSEokWCEL_HCLHOWinSizeOFFInterference55TRUE555555555555RNFCSLHOCmAllowedNRT11TRUEWCEL_HCLHOWinSizeOFFResRateSC55TRUE555555555555RNFCSignConnActivitySupervision44TRUEWCEL_HCLHOWinSizeONCapaReqRejRate00TRUE000000000000RNFCWPSCallRestriction00TRUEWCEL_HCLHOWinSizeONHardBlocking00TRUE000000000000RNFCWireLessPriorityService00TRUEWCEL_HCLHOWinSizeONInterference00TRUE000000000000RNHSPAWeightForARP1100100TRUEWCEL_HCLHOWinSizeONResRateSC00TRUE000000000000RNHSPAWeightForARP2100100TRUEWCEL_HCLoadBasedCPICHEcNoSRBHSPA-25-25TRUE-25-25-25-25-25-25-25-25-25-25-25-25RNHSPAWeightForARP3100100TRUEWCEL_HCLoadBasedCPICHEcNoThreEDCH2MS00TRUE000000000000RNHSPAATOSRBsOnHSPA3030TRUEWCEL_HCMBLBInactivityEnabled00TRUE000000000000RNHSPAN10msCPCOptObjective11TRUEWCEL_HCMBLBMobilityEnabled00TRUE000000000000RNHSPAN10msCQIDTXTimer77TRUEWCEL_HCMBLBRABSetupEnabled01FALSEMBLB enabled sitesYes000000001111RNHSPAN10msCQIFeedbackCPC44TRUEWCEL_HCMBLBRABSetupMultiRAB11TRUE111111111111RNHSPAN10msInacThrUEDRXCycle77TRUEWCEL_HCMBLBStateTransEnabled01FALSEMBLB enabled sitesYes000000001111RNHSPAN10msInacThrUEDTXCycl233TRUEWCEL_HCMIMOHSDPACapaHO00TRUE000000000000RNHSPAN10msMACDTXCycle11TRUEWCEL_HCMaxNumberUECmSLHO66TRUE666666666666RNHSPAN10msMACInacThr00TRUEWCEL_HCNrtFmcgIdentifier32364044RNHSPAN10msUEDPCCHburst100TRUEWCEL_HCNrtFmciIdentifier32364044RNHSPAN10msUEDPCCHburst200TRUEWCEL_HCNrtFmcsIdentifier32364044RNHSPAN10msUEDRXCycle22TRUEWCEL_HCPFLIdentifier47484950RNHSPAN10msUEDTXCycle122TRUEWCEL_HCRTWithHSDPAFmcgIdentifierTRUE34384246RNHSPAN10msUEDTXCycle222TRUEWCEL_HCRTWithHSDPAFmciIdentifier34384246RNHSPAN10msUEDTXLongPreamble11TRUEWCEL_HCRTWithHSDPAFmcsIdentifier34384246RNHSPAN2msCPCOptObjective11TRUEWCEL_HCRTWithHSPAFmcsIdentifier34384246RNHSPAN2msCQIDTXTimer77TRUEWCEL_HCRtFmcgIdentifier31353943RNHSPAN2msCQIFeedbackCPC33TRUEWCEL_HCRtFmciIdentifier31353943RNHSPAN2msInacThrUEDRXCycle77TRUEWCEL_HCRtFmcsIdentifier31353943RNHSPAN2msInacThrUEDTXCycl255TRUEWCEL_HCServHONumbUEInterFreq12FALSEService and Load Based feature related parameter222222222222RNHSPAN2msMACDTXCycle33TRUEWCEL_HCServHONumbUEInterRAT11TRUE111111111111RNHSPAN2msMACInacThr00TRUEWCEL_HCServHOPeriodInterFreq00TRUE000000000000RNHSPAN2msUEDPCCHburst100TRUEWCEL_HCServHOPeriodInterRAT00TRUE000000000000RNHSPAN2msUEDPCCHburst200TRUEWCEL_LCMaxIncrInterferenceUL1010TRUE101010101010101010101010RNHSPAN2msUEDRXCycle22TRUEWCEL_LCNonHSEventECommMeas10FALSEno value000000000000RNHSPAN2msUEDTXCycle133TRUEWCEL_LCPrxMeasFilterCoeff22TRUE222222222222RNHSPAN2msUEDTXCycle244TRUEWCEL_LCPrxNoise-1050-1050TRUE-1050-1050-1050-1050-1050-1050-1050-1050-1050-1050-1050-1050RNHSPAN2msUEDTXLongPreamble11TRUEWCEL_LCPrxNoiseAutotuning11TRUE111111111111RNHSPAS10msCPCOptObjective11TRUEWCEL_LCPrxOffset1010TRUE101010101010101010101010RNHSPAS10msCQIDTXTimer77TRUEWCEL_LCPrxTarget4080FALSEokYes808080808080808080808080RNHSPAS10msCQIFeedbackCPC44TRUEWCEL_LCPrxTargetMax6553565535TRUE655356553565535655356553565535655356553565535655356553565535RNHSPAS10msInacThrUEDRXCycle77TRUEWCEL_LCPrxTotalReportPeriod800FALSEno value000000000000RNHSPAS10msInacThrUEDTXCycl233TRUEWCEL_LCPtxMeasFilterCoeff22TRUE222222222222RNHSPAS10msMACDTXCycle11TRUEWCEL_LCPtxOffset105FALSEokYes5555555555555555RNHSPAS10msMACInacThr00TRUEWCEL_LCPtxTarget400455FALSEdepends on power settings. Refer Power settings.Refer to worksheet " summary configuration"425473443455RNHSPAS10msUEDPCCHburst100TRUEWCEL_LCPtxTotalReportPeriod800FALSEno value000000000000RNHSPAS10msUEDPCCHburst200TRUEWCEL_LCRACHloadReportPeriod800FALSEno value000000000000RNHSPAS10msUEDRXCycle22TRUEWCEL_LCRACHmeasFilterCoeff1010TRUE101010101010101010101010RNHSPAS10msUEDTXCycle122TRUEWCEL_LCRSEPSEventECommMeas10FALSEno value000000000000RNHSPAS10msUEDTXCycle222TRUEWCEL_LCRTWPEventECommHyst200FALSEno value000000000000RNHSPAS10msUEDTXLongPreamble11TRUEWCEL_LCRTWPEventECommMeas10FALSEno value000000000000RNHSPAS2msCPCOptObjective11TRUEWCEL_LCRTWPMeasFilterCoeff20FALSEno value000000000000RNHSPAS2msCQIDTXTimer77TRUEWCEL_LCTCPEventECommHyst200FALSEno value000000000000RNHSPAS2msCQIFeedbackCPC33TRUEWCEL_LCTCPEventECommMeas10FALSEno value000000000000RNHSPAS2msInacThrUEDRXCycle77TRUEWCEL_LCTCPMeasFilterCoeff20FALSEno value000000000000RNHSPAS2msInacThrUEDTXCycl255TRUEWCEL_LCVoiceOverrideSTHSUPA11TRUE111111111111RNHSPAS2msMACDTXCycle33TRUEWCEL_PCDPCModeChangeSupport11TRUE111111111111RNHSPAS2msMACInacThr00TRUEWCEL_PCPRACHRequiredReceivedCI-25-20FALSEok-20-20-20-20-20-20-20-20-20-20-20-20RNHSPAS2msUEDPCCHburst100TRUEWCEL_PCPTxPICH-8-8TRUE-8-8-8-8-8-8-8-8-8-8-8-8RNHSPAS2msUEDPCCHburst200TRUEWCEL_PCPowerOffsetLastPreamblePRACHmessage2-3FALSEok-3-3-3-3-3-3-3-3-3-3-3-3RNHSPAS2msUEDRXCycle22TRUEWCEL_PCPO1_1588TRUE888888888888RNHSPAS2msUEDTXCycle133TRUEWCEL_PCPO1_301212TRUE121212121212121212121212RNHSPAS2msUEDTXCycle244TRUEWCEL_PCPO1_601616TRUE161616161616161616161616RNHSPAS2msUEDTXLongPreamble11TRUEWCEL_PCPowerRampStepPRACHpreamble23FALSEok333333333333RNHSPAV10msCPCOptObjective11TRUEWCEL_PCPtxAICH-8-3FALSEok-3-3-3-3-3-3-3-3-3-3-3-3RNHSPAV10msCQIDTXTimer66TRUEWCEL_PCPtxBCCHHSPDSCH700FALSEno value000000000000RNHSPAV10msCQIFeedbackCPC44TRUEWCEL_PCPtxBCCHHSSCCH-200FALS