3GKPIPhaseFail categoryFail causeSolutionAccessibilityVFRRRC PhaseSetup failsAC failDL power/loadCheck DL code blocking( CodeTreeOptTimer(3600), CodeTreeUsage( 40%), CodeTreeOptimisation(1), AMROverSC(90%), AMRTargetSC( 70%))UL interference/load1)Reduce tilt, CPICH power or add new carrier/site2) Direct traffic to other layerCode blocking1) Code tree optimiation2) Recommend for additional carrier or secondary Scrambling codesBTS failCE utilization ( add CE or LCG split )1) Add CE2) LCG Split ( Logical Channel Group)3) Change TCELL value (SFN Scheduler)4) Change LCG partitioningHardware issueCheck hardwareSite alarmClear alarmsTransp/Iub FailsIub utilizationNumber of E1 presentAdd E1s if requiredRNC failCheck COCO configSRNC relocation issuesRNC CapacityRNC alarms/RNC faultAccess FailsRadio failCheck PRACH distribution for overshootingRecommend tilt for overshooting cellsEc/No distribution - Missing neighbours or pilot pollutionAdd missing neighbours or reduce tilt of overshooting neighbouring cellsRTWP distributionCheck for high load or MHA setting Check status of neighbouring cell Check cell availability and alarms in neighbouring cellsUu failsUL/DL synchronisationCheck Tx/Rx power parameterRNC failCheck COCO configSRNC relocation issuesRNC CapacityRNC alarms/RNC faultRAB PhaseSetup failsAC failDL powerCheck DL code blockingUL interfernce1)Reduce tilt, CPICH power or add new site2) Direct traffic to other layerCode occupancy1) Code tree optimiation2) Recommend for additional carrier or secondary Scrambling codesBTS failCE utilization ( add CE or LCG split )1) Add CE2) LCG Split3) Change TCELL value4) Change LCG partitioningHardware issueCheck hardwareSite alarmClear alarmsTransp/Iub FailsIub utilizationNumber of E1Add E1s if requiredRNC failCheck COCO configSRNC relocation issuesRNC CapacityRNC alarms/RNC faultAccess FailsUE failCheck counters M1006C192 & M1006C193check if issue is from a particular UE or due to radio condition Check activation time offsetOptimize activation time offsetRNC failCheck COCO configSRNC relocation issuesRNC CapacityRNC alarms/RNC faultPS Access Failure RateSetup failsAC failDL powerCheck DL code blockingUL interfernce1)Reduce tilt, CPICH power or add new site2) Direct traffic to other layerCode occupancy1) Code tree optimiation2) Recommend for additional carrier or secondary Scrambling codesBTS failCE utilization1) Add CE2) LCG Split3) Change TCELL value4) Change LCG partitioningHardware issueCheck hardwareSite alarmClear alarmsRNC failCheck COCO configSRNC relocation issuesRNC CapacityRNC alarms/RNC faultAccess FailsUE failCheck counters M1006C192 & M1006C193check if issue is from a particular UE or due to radio condition Check activation time offsetOptimize activation time offsetRNC failCheck COCO configSRNC relocation issuesRNC CapacityRNC alarms/RNC faultHSDPA PS AFRSetup FailsRNC failRNC CapacityRNC alarms/RNC faultBTS FailCheck CE utilization ( UL CE ) and add CE if required1) Add CE2) LCG Split3) Change TCELL value4) Change LCG partitioningHardware issueCheck hardwareSite alarmClear alarmsIub failIub utilizationNumber of E1Add E1s if requiredUE failCheck counters M1006C192 & M1006C193check if issue is from a particular UE or due to radio condition Check activation time offsetOptimize activation time offsetUL DCH FailCheck UL Load1)Reduce tilt, CPICH power or add new carrier/site2) Direct traffic to other layerMax user failCheck max HSDPA users in the cellIf max user capacity is reached add additional HSDPA user licenceHSDPA User licence in the CellIf max user capacity is reached add additional HSDPA user licenceTCELL valuesIf max possible user licence is used, TCELL values can be changed to change scheduler mappingHSUPA PS AFRSetup failsMax user failCheck max HSUPA users in the cellIf max user capacity is reached add additional HSDPA user licenceHSUPA User licence in the CellIf max user capacity is reached add additional HSDPA user licenceTCELL valuesIf max possible user licence is used, TCELL values can be changed to change scheduler mappingBTS failCheck CE utilization ( UL CE ) and add CE if required1) Add CE2) LCG Split3) Change TCELL value4) Change LCG partitioningBTS HW FailHardware issueCheck hardwareSite alarmClear alarmsTransp failIub utilizationNumber of E1Add E1s if requiredUE failCheck counters M1006C192 & M1006C193check if issue is from a particular UE or due to radio condition Check activation time offsetOptimize activation time offsetRetainabilityVoice drop rateIU FailRadio failCheck PRACH distribution for overshootingRecommend tilt for overshooting cellsEc/No distribution - Missing neighbours Add missing neighbours or reduce tilt of overshooting neighbouring cellsBTS FailCheck CE utilization ( UL CE ) and add CE if required1) Add CE2) LCG Split3) Change TCELL value4) Change LCG partitioningHardware issueCheck hardwareSite alarmClear alarmsRNC failCheck COCO configSRNC relocation issuesRNC CapacityRNC alarms/RNC faultUE failCheck Channel recofiguration failure rateCheck IFHO, ISHO & code optimizationCheck activation time offsetOptimize activation time offset( 300 ms)Trans failIub utilizationNumber of E1Add E1s if required

Packet RAB drop rateIU FailRadio failCheck PRACH distribution for overshooting(PRACHDelayRange(20),PRACHRequiredReceivedCI(-25), PRACH_preamble_retrans( 8)Recommend tilt for overshooting cellsEc/No distribution - Missing neighbours Add missing neighbours or reduce tilt of overshooting neighbouring cellsBTS FailCheck CE utilization ( UL CE ) and add CE if required1) Add CE2) LCG Split3) Change TCELL value4) Change LCG partitioningHardware issueCheck hardwareSite alarmClear alarmsRNC failCheck COCO configSRNC relocation issuesRNC CapacityRNC alarms/RNC faultUE failCheck Channel recofiguration failure rateCheck IFHO, ISHO & code optimizationCheck activation time offsetOptimize activation time offsetTrans failIub utilizationNumber of E1Add E1s if requiredHSDPA PS DCRRL FailCheck NeighboursAdd missing neighbours. Check if neighbouring cells HSDPA is enabledSCC failsCheck for radio, Iub congetion and CE utilizationCQI distributionImprove coverage and eliminate interfering neighboursMobility FailCheck Mobility parametersOptimize Add/Drop windowHSUPA PS DCRSCC failsCheck Radio, AC & BTS failsCheck radio conditions, overshooting, neighbour addition & max number of usersDL congestionCheck Code blockingCE utilization1) Add CE2) LCG Split3) Change TCELL value4) Change LCG partitioningOther failsRNC failureCheck for RNC internal capacity, SRNC relocation fails

2GReduce DL InterferenceDrop CallSolutionReduce DL BTS PowerInterference DL/UPFreq PlanAntenna Parameter( Tilt, Height, Gain, Type, Cable )Poor RX LevelCheck HW or Plan New Site or Change Antenna Parameters, TMA or TMB PlanPower control ParametersPoor Link BalanceCheck HW and Power control parameters, DL or UL limitated SystemTune Freq. PlanHW issuesTRX Faulty, TSL Faulty, Repeater could be, Div issues,Define Dominance AreaSync OSS Adj. relationshipAbis failuredue to LAPD overloading, Telecom link overload( 2720 ) 16 kbps to 32 kbpsDefine missing NbrAbis failureMW link or Sync Check TRX quality and Change TRP to best Quality TRXAbis failureAbis related counter getting updated due to wrong reasons T3101(T200), T3707 - TRCCheck HW problem, related to Downlink PathTranscoder FailureUnsync clear call in Abis and A interface. Change Transcoder or locking and unlocking can work Alarm No. 2992 and 2993Search External Interference sourceBCSU LoadingDistribute sites to the other less loaded BCSU, Cell Doctor , BSCU reset due to overloading of no of TCH TSLOvershooting from other possible Co-Ch CellsCo BCCH and BSIC NbrsFine tune Freq plan of Adj cell Wrong Nbr PlanningFine tune Nbr relationship using 153 reportA interface failureLock those pool and change ET card or Transcoder, Lock and unlock resourcesWrong BSS ParametersCheck Actual Vs. PlanLong Distance CallInstall TMA or TMB or reduce cell range for link balanceFreq Plan Hopping or BCCH layer interference and fine tuneBlocking - Most IMPAdd more TRX or SiteWrong KPI formulaCorrect Actual vs. Cell doctor DCR_3i or DCR_4eLock bad performing TRX SDCCH DropSame reason like TCH DropTime slot is faultyChange TSL or TRXShift SD from bad quality TRX to good quality TRXBlocking SDBlocking TCHHandover success RateAdd SDsAdd TRXAMR HO Fail due to TCH rejection due to A inter CRCDynamic SDCCH Add Dual rate with AMRTarget cell is congested or blockedLAC boundryconfig. Dynamic SDNbr is not properQueuing can removed Directed retryQuality of target cell is badQueuingNo dominace cellFreq HoppingInterferenceIUOWrong freq plan between source and Nbr or between NbrsAMH+TRHO+UMHandover related parameters and hopping planICESpeed of MSDFCAPoor RQ levelFlexible MAIO TRX signalling loadDual BandUplink and DL interferenceMicro cell and Pico Cell Street CellsReduce Cell range

LTE DimensioningLTE has many parameters that have to be dimensioned or planned:

Parameters to be dimensionedCyclic PrefixControl Format IndicatorPHICH durationPHICH scaling factorOther Reference SignalsParameters to be planned (assigned)Physical Cell Identification (PCI)PRACH parameter planningPreamble formatPRACH configuration indexZero correlation zoneRoot Sequence IndexFrequency OffsetUplink Reference Signal SequenceCell and BTS Identity PlanningTracking AreasNeighborhood PlanningLTE resources have to be optimized, as in any cellular network, with considerations for ICIC and other techniques

Resource Allocation in LTEControl, Traffic and SignalingInterference AnalysisSNR and SNIR, FEC, H-ARQResource Reuse analysis in LTEReuse of 1 x Reuse of nFrequency PlanningTraffic Resource PlanningAllocation schedulersFrequency segmentationTime zoningControl Resource PlanningCan it be done?

Let us understand peak data rate or LTE throughput calculation with following LTE system configuration.

20MHz channel, 4x4 MIMO configuration, Theoretically, Peak Data rate= No. of REs per subframe x no. of bits per modulation symbol=No of resource element per scheduling block* No of Scheduling block per 20 Mhz *no. of bits per modulation symbol =No of resource block per Resource block *2* No of Scheduling block per 20 Mhz* no of bits per modulation symbol=84*2*100*6 per 1ms=16800 x 6 per 1ms=100800 bits/ 1 msData Rate=100.8Mbps For 4x4 MIMO data rate=403Mbps

About 25% of overhead is used here for RS(reference signal), synchronization signals, PDCCH, PBCH & for some coding. This leads to effective data rate of about 403Mbps X 0.75 = 302Mbps.Each of the Resource Element(RE) will carry a modulation symbol.

Another way for LTE throughput calculation is to use Table number 7.1.7.1-1 which gives Transport Block Size(TBS). TBS indicates No. of bits that can be transmitted in one subframe per Transmit Time Interval. From the table with RBs of 100 and TBS index of 26, Transport Block Size is 75376. For MIMO configuration of 4x4, we will get about data rate(peak) about 75376 x 4 per 1ms. This leads to effective peak data rate of 301.5 Mbps.

UMTS Channel

RADIO UMTSEc/No= RSCP / RSSI (dB)2. RSCP The Received Signal Code Power (RSCP) is the collected RF energy after the correlation / descrambling process, usually given in dBm. Because this process already filters out the signal with the correct code (the code meant for the specific UE), the RSCP can not be calculated back to the total received RF power that a normal monitoring receiver or spectrum analyzer measures. Instead, a correlation receiver has to be used and the RSCP has to be measured for the specific code only, in the code domain. Only this code power is of interest for the following receiver stages when judging on the quality of the reception. A commercial UMTS receiver has to know the code that is transmitted for it in order to perform the correlation process. With monitoring equipment, however, we want to measure UMTS emissions with any code. Therefore, special measurement receivers and equipment are necessary for UMTS measurements. These receivers have to try and correlate the received pseudo-noise-like signal with every possible code. This process is called PN scanning. Only after the receiver has found a match, the descrambling can take place, followed by measurement of the RSCP in the code domain. 2.3 Ec/I0This is the ratio of the received energy per chip (= code bit) and the interference level, usually given in dB. In case no trueinterference is present, the interference level is equal to the noise level. However, in a UMTS network the UE normally receives signals from multiple base stations, all transmitting on the same frequency. Therefore it is possible that even at a location close to a base station, with a high RSCP, no logon is possible, due to high interference levels from a second nearby base station. This effect is called pilot p2.4 RSSI The Received Signal Strength Indicator (RSSI) is a value that takes into account both RSCP and Ec/I0. It is usually given in dBm and can be calculated as follows: RSSI [dBm] = RSCP [dBm] - Ec/I0 [dB] (1) As with RSCP and Ec/I0, it can only be measured in the code domain and needs the special monitoring equipment as described above.RTWP: Received total wideband power: Represents a measure of UMTS technology: the total level of noise within the UMTS frequency band of any cell.RTWP is related to uplink interference, and its monitoring helps control the call drops - mainly CS. It alsohas importance in the capacity management, as it provides information for the Congestion Controlregarding Uplink Interference.In UMTS, the uplink interference may vary due to several factors, such as the number of users in thecell, the Service, Connection Types and Conditions of Radio, etc..In a network is not loaded, normal, acceptable RTWP Average value is generally around -104.5 and-105.5 dBm.For cases in which cell has two carriers, the difference between them RTWP should not exceed 6 dB.RTWP can cause performance degradation, mainly CS Call Drops.If RTWP is not at acceptable levels, some actions should be taken.1.The first thing to do is check if there is a configuration issue with the RNC or NodeB. This is the most common case,especially in cases of new activations.2.Once verified the parameter settings, the next step is the physical examination, especially jumpers and cables, oftenpartially reversed. It also should be checked if there is faulty transmitters, or any other problem that could generateintermodulation between the NodeB and the antenna.3.If the parameter settings and hardware are ok, the chance is very high that we have external interference, such as aInterferer Repeater.Received total wideband power- It simply represents the interference level on a cell.Interference could be normal (because of increased number of users)or Abnormal (because of hardware issues or external interference).RTWP is also known as UL RSSI.

HSDPAHSDPA was introduced in Release 5 of 3GPP.The main features coming with HSDPA are:1. Use of multiple SF16 shared physical channels. At SF 16 there can be 16 possible channels. Out of which 1 SF branch code channel is used to carry the common control channel like P-CCPCH, S-CCPCH, HS-SCCH, CPICH, P-SCH, S-SCH, AICH, PICH.2. Shorter TTI of 2ms is implemented. This enables faster Re-Transmission mechanism.3. Use of higher order modulation scheme like 64 QAM.

So now the HSDPA Tput calculations goes like:

HSDPA Tput = ( (chiping rate / Spreading factor) * number of codes) * ( data bits per symbol for 64QAM).

= ( ( 3.84 * power(10,6) / 16 ) * 15 ) * 4

= 14.4 Mbps.