2g Radio Network Optimization Training ( Practical Workshop)

Slide 1

7FACCH MESSAGESConnection establishment from SDCCH to TCHEnd validation of a SDCCH-TCH commutationCharacteristics of the future used BS after handoverConnection establishment to BS after handoverValidation of an handoverSACCH MESSAGESMeasures:power level of the communicationquality level of the communicationlevel on the beacon frequency of the neighboring cells Timing AdvancePower ControlSMSTCH MESSAGESSpeechDataHandover Access message (uplink)SDCCH MESSAGESRequest for a SDCCH assignmentRequest for the end of channel assignmentOrder of commutation from SDCCH to TCHSMSLogical Channel Description (1/2)Soc Classification level # Nokia Siemens Networks7Slow Associated Control CHannel (SACCH)SACCH is a dedicated signaling channel associated with SDCCH or TCH. It is used to carry:on the uplink path: radio measurements, Layer 1 Header and Short Messages (SMS),on the downlink path: System Information type 5, 5bis, 5ter and 6, Layer 1 Header and Short Messages (SMS).These messages give information about quality of the communication (UL), Location Area Identity (DL), Cell Identity (DL), Neighboring Cells Beacon Frequencies in dedicated mode (DL), NCC permitted (DL), Cell Options (DL), Power Control (Layer 1 Header- UL/DL), Timing Advance (UL/DL).Standalone Dedicated Control CHannel (SDCCH)SDCCH is a dedicated and consequently a duplex channel. This channel transmits signaling messages for link establishment, location update, SMS, authentication of the subscriber, ciphering command and answer, and all kinds of supplementary services.Course Outline DAY 1---CALL FLOW ( MTC& MOC)& Network Optimization Principles( Parameters ,Hoc, Poc, Timers)

DAY2- Network Performance Optimization(Counters, KPIs, ND Reports)

DAY 3-- AMR TRAINING & FEATURES PRESENTATION(Robust AMR , AMR PPC, SAL)

Soc Classification level # Nokia Siemens NetworksContentsPresentation / Author / Date Channels Basics

Mobile Originated CallMOC

Mobile Terminating CallMTC Handover control ---HOC

Power Control POC

Parameters

Timers Soc Classification level # Nokia Siemens Networks4Logical Channels on Air interfaceLOGICALCHANNELSCOMMONCHANNELSDEDICATED CHANNELSBROADCAST CHANNELSCOMMONCONTROLCHANNELSDEDICATED CONTROL CHANNELS TRAFFIC CHANNELSFCCHBCCHSCHSDCCHSACCHFACCHPCHAGCHRACHTCH/FTCH/EFRTCH/H# Nokia Siemens NetworksR 255 G 211 B 8R 255 G 175 B 0R 127 G 16 B 162R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 175 G 0 B 51R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 52 G 195 B 51Primary colors:Power Control Motivation

Longer service time of battery

Realization of power classReduced interference on DL/ULActivation of DL power control

powerCtrlEnabledY,NPower control independent

for DL and ULfor each callSoc Classification level # Nokia Siemens Networks30 dB Range

Power classdependentrange

AttenuationsPower ValuesPower Control ParameterOutput Power LimitsMaximum MS output power

msTxPwrMaxGSM5..39 dBm GSM 900 TCHmsTxPwrMaxGSM1x000..36/32,33 dBm GSM 1800/1900 TCHmsTxPwrMaxCCH5..39 dBm GSM 900 CCHmsTxPwrMaxCCH1x000..30 dBm GSM 1800 CCH0..32 dBm GSM 1900 CCH

Minimum MS output power

minMSTxPower5..39 dBm GSM 9000..36 dBm GSM 18000..32 dBm GSM 1900Maximum BTS output power (by minimum attenuation)

bsTxPwrMax0..30 dB GSM 900bsTxPwrMax1x00 0..30 dB GSM 1800/1900

Minimum MS output power (by maximum attenuation)

bsTxPowerMin0..30 dB

Additional attenuation for super reuse TRx

bsTxPowerOffset0..30 dBSoc Classification level # Nokia Siemens NetworksPower Control ParametersPower Change Step SizesFixed increment step size

powerIncrStepSize2,4,6 dB

Fixed decrement step size

powerDecrStepSize2,4,6 dBDesired power level can be achieved in 1 or 2 commandsYesFixed step sizeNoVariable step sizeSoc Classification level # Nokia Siemens NetworksPower Increase Due to Signal LevelpcLowerThresholdsLevelDL/ULPower control triggeredUL: Power increase of MSDL: Power increase of BTSRXLEV_DL/UL > pcLowerThresholdLevelDL/UL - 2 powerIncrStepSize YesFixed step size

PWR_INCR_STEP = powerIncrStepSizeNoVariable step size

PWR_INCR_STEP = pcLowerThresholdLevelDL/UL RXLEV_UL/DLActual receive level RXLEV_DL/ULSoc Classification level # Nokia Siemens NetworksLower LevelUpper LevelUpper QualityLower QualityPower Control SummaryNo actionPower decreasedue to levelPower increasedue to qualityPower increasedue to levelor qualityPower increasedue to qualityPower decreasedue to levelor qualityPower increasedue to levelPower decreasedue to quality6 dBPower increasedue to levelSoc Classification level # Nokia Siemens NetworkshoThresholdLevDL = -95 dBm/Px: 1, Nx: 1hoMarginLevel = 3 dBRx Level Handover(Example)enableHandoverMarginLevQual = YBTS output power= MaximumAdjacent cells evaluationConditions 1a and 2b:AV_RXLEV_NCELL AV_RXLEV_DL_HO > hoMarginLevel fulfilledIf no adjacent -> HO Fail

-95-100-90Serving cellRX LevelhoThresholdLevelDLLevel Threshold is exceeded (bad_RxLevel)LEVEL HOHO-95-100-90Serving cellAdjacent cell(n)RX Level3 dBt1t1t2t2Suitable target cell:RxLev(n) RxLev+3dBSoc Classification level # Nokia Siemens Networkst1:hoThresholdLevDL < -95Px=1, Nx=1-> HO triggered -> No suitable target cell -> HO fail

t2:hoThresholdLevDL < -95Px=1, Nx=1AV_RXLEV_NCELLAV_RXLEV_DL_HO > hoMarginLev (=3)-> HO triggered -> suitable target cell -> HO successful

PBGT > hoMarginLev/Qual(n) PBGT = (AV_RXLEV_NCELL(n) - AV_RXLEV_DL_HO) - (btsTxPwrMax - BTS_TXPWR)2bPBGT > hoMarginPBGT(n)PBGT = (msTxPwrMax - msTxPwrMax(n)) (AV_RXLEV_DL_HO - AV_RXLEV_NCELL(n)) - (btsTxPwrMax - BTS_TXPWR)2aGeneral caseHandover Strategy(Decision due to Power Budget)Handover due to RX level, RX quality, distance and umbrella handoverPower budget margin to prevent repeated handovers between adjacent cellshoMarginPBGT-24..63 dBgeneral case

RX level and RX quality margins to prevent repeated handovers between adjacent cellshoMarginQual-24..24 dBhandover due to signal qualityhoMarginLevel-24..24 dBhandover due to signal levelEnableHOMarginLevQualY/Nrequired to enable marginsSoc Classification level # Nokia Siemens NetworksInterference Handover(Parameters)Thresholds

hoThresholdsInterferenceDL/UL-110..-47 dBmhoThresholdsQualDL/UL0..7

Intra / inter cell handover

hoPreferenceOrderInterDL/UL INTRAfor network without frequency hoppingINTERfor network with frequency hoppingenableIntraHOInterDL/UL Y/Nrequired to enable intra cell handoverSoc Classification level # Nokia Siemens NetworksInterference Handover(Execution)AvRX level hoThresholdsInterferenceDL/ULANDAvRX quality value hoThresholdsQualDL/ULRanking of adjacent cellsenableHOMarginLevQual = YenableHOMarginLevQual = NCheck of adjacent cells with conditions 1a and 2bCheck of adjacent cells with conditions 1a and 2aSuitable adjacent cell ?YesNoInter cell handoverIf enabled Intra cell handoverOtherwise Handover failureSoc Classification level # Nokia Siemens NetworkshoThresholdQualDL= 4/Px:4, Nx:6hoThresholdInterferenceDL = -85 dBm/Px:1, Nx:1hoMarginQual= 0 dBInterference Handover(Example)hoPreferenceOrderInterfDL = INTERenableHandoverMarginLevQual = YBTS output power= MaximumBOTH the Quality and Interference Threshold is exceeded (bad_RxQuality/good_RxLevel)INTERFERENCE HOAdjacent cells evaluationConditions 1a and 2b:AV_RXLEV_NCELL AV_RXLEV_DL_HO > hoMarginQual fulfilledIf no adjacent -> Intra HO-85-90-80Serving cellAdjacent cell(n)RX LevelSuitable HO target cell:RxLev(n) RxLevhoThresholdInterferenceDLt1t2RX QualityhoThresholdQualDL34256Serving cellt1t2Adjacent cell(n)HOSoc Classification level # Nokia Siemens Networkst1:hoThresholdQualDL > 4hoThresholdInterferenceDL > -85-> HO triggered (not triggering attempt counter)AV_RXLEV_NCELLAV_RXLEV_DL_HO < hoMarginQual (=0)-> No suitable target cell -> Intra HO not possible -> HO fail (not triggering failure counter)

t2:hoThresholdQualDL > 4hoThresholdInterferenceDL > -85-> HO triggeredAV_RXLEV_NCELLAV_RXLEV_DL_HO > hoMarginQual (=0)-> HO successful

RX Quality Handover(Execution)AvRX quality value hoThresholdsQualDL/ULRanking of adjacent cellsenableHOMarginLevQual = YenableHOMarginLevQual = NCheck of adjacent cells with conditions 1a and 2bCheck of adjacent cells with conditions 1a and 2aSuitable adjacent cell ?YesNoInter cell handoverHandover failureThresholdshoThresholdsQualDL/UL0..7Soc Classification level # Nokia Siemens NetworksSummary of parametersBTS Parameters - BLT, REO, MADR, MIDR, RE

HOC Parameters - IDR, IDN, IDP, IUN, IUP, LDR, LUR, LDW, LUW, QDW,QUW, EIH & EIC

POC Parameters - LDW, LUW, QDW, QUW, INT, LDR, LUR, LDN, LUN, UDR & UUR.

Adjacency Parameter SL to be implemented.

BSC Parameters - ITCF to be implemented.

Increase MFRMS 4 to 5 in those few cell having Page deletion

RACH DELETION -Lapd load increase from 32kbs to 64kbs-max load crossing the threshold limit.

Soc Classification level # Nokia Siemens Networks69Company ConfidentialWithin the CCCH_Group , Mobile listen to paging in specific paging (CCCH) blocks onlyThe block specific to a mobile is its Paging Group

Paging GroupSoc Classification level # Nokia Siemens NetworksCompany Confidential12/17/2013Author: Arif R.17Company ConfidentialAvailable Paging Blocks = CCCH Blocks -- bs_ag_blks_res Maximum AGCH Reservation for Non-Combined = 7 Available Paging Blocks = 2 Maximum AGCH Reservation for Combined = 2Available Paging Blocks = 1

Mimimum AGCH Reservartion for Non-Combined = 0 Available Paging Blocks = 9Minimum AGCH Reservation for Combined = 0 Available Paging Blocks = 3 No of Paging Blocks will have a range of 1 - 9Available Paging Blocks on 1 CCCH_GroupPagingSoc Classification level # Nokia Siemens NetworksCompany Confidential12/17/2013Author: Arif R.19Company ConfidentialMobile belonging to Paging Group P0 will remain idle during P1 ,P2,P3

Mobile utilizes power only during PO. This is known as DRXBS_PA_MFRMS-- No of Multiframes after which Same Paging Group is repeated-- This Parameter is broadcasted on BCCH-- Ranges between 0 -- 9 Multiframes

PagingSoc Classification level # Nokia Siemens NetworksCompany Confidential12/17/2013Author: Arif R.20Company ConfidentialNo of Paging Groups = Paging Blocks x Repitition of Paging BLock N = [ CCCH - bs_ag_blks_res ] x bs_pa_mfrmsMinimum Available Paging Groups = Min Pag blocks x Min bs_pa_mfrms = 1 x 1 = 1Maximum Available Paging Groups = Max Pag blocks x Max bs_pa_mfrms = 9 x 9 = 81Range of Paging Groups on 1 CCCH_GroupTotal No of Paging Groups on 1 CCCH_Group ( N )PagingSoc Classification level # Nokia Siemens NetworksCompany Confidential12/17/2013Author: Arif R.21Company ConfidentialHow does a Mobile knows it CCCH_Group Paging Group No ?Pag Grp No = [ ( IMSI mod 1000 ) mod ( BS_CC_CHANS x N ) ] mod NN = Total Paging Groups = No of Paging Blocks x bs_pa_mfrmsCCCH_Group = [ ( IMSI mod 1000 ) mod ( BS_CC_CHANS x N ) ] div NPagingSoc Classification level # Nokia Siemens NetworksCompany Confidential12/17/2013Author: Arif R.2224 2005 Nokia V1-Filename.ppt / 2005-02-15/ srCALCULATIONSo the calculation {(IMSI mod 1000) mod [BS_CC_CHANS*N]} mod N based on the information in the previous slide would be as follows:{(460003811319045 mod 1000) mod [ 9 * 28 ]} mod 28

STEP1. (IMSI mod 1000) = (460003811319045 mod 1000) 460003811319045 / 1000 = 460003811319.045 mod then requires removing the whole number and multiplying the remainder by the original mod number. This would give 0.045 *1000 = (45)

STEP2.From previous slide, (BS_CC_CHANS*N) BS_CC_CHANS = 9Number of Paging Groups (N) = 28 (9 * 28) = (252)

STEP3.{(IMSI mod 100)mod[BS_CC_CHANS*N]} = {(45) mod [252] }45 / 252 =0.1785mod requires removing the whole number however as there is no whole number in this case then the remainder is multiplied by 252. This would give 0.1785 * 252 = 44.982 (Round up to 45)

STEP4. Result obtained in Step 3, mod 28, therefore: (45) mod 2845 / 28 = 1.6071mod requires removing the whole number and multiplying the remainder by the original mod number.This would give 0.6071 * 28 = 17Therefore we conclude that IMSI 460003811319045 belongs to Paging Group 17.

For More information on Paging Groups see GSM Specification 05.02.Soc Classification level # Nokia Siemens Networks25 2005 Nokia V1-Filename.ppt / 2005-02-15/ srMODULUS EXPLAINEDWhat is MODULUS?If you divide 14 by 4 you get an answer of 3 plus a remainder of 2.When using MODULUS the remainder is the important bit, the whole number is discarded.Example 14/4 = 3 remainder 2, discard the whole number (3) leaving the answer 2, the maths for this would be written in the form: [14] mod 2.

Soc Classification level # Nokia Siemens NetworksMTC _CALL FLOWPSR = (first paging response+ repeated paging response)*100/first paging request The following formula indicates the success rate of paging (call & SMS) 100* sum(succ_page)/sum(fail_page+succ_page) Paging (MSC to BSC ;BSSMAP)This message is sent by MSC when it has found out the called MS is somewhere under him (= MSC recognises this is a GSM_END -call). This message contains mainly four kind of information: message type, IMSI of the called subscriber, TMSI of the called subscriber and Cell Identifier list. If TMSI -numbers are defined for use these have the priority one, for security reasons and if the network does not use TMSIs then IMSI -number is included only. The paging is sent as an UDT (Unit Data) message to the BSC.

Paging Command (BSC to BTS ;BTSM) The BSC always calculates so-called paging group. The idea of this calculation is to find out in which radio time slots the BTS can send the Paging Requests out towards the MS. Reason: in the network, there is a possibility to have at least three different kind of BCCH-TRX -radio time slot configurations and thus logical channel PCH can have at least three different kinds of location. If the BSC receives both TMSI and IMSI from the MSC, then it uses always TMSI number when sending paging further on.

Paging Request (BTS to MS;PCH)The BTS sends paging on a PCH channel.

Presentation / Author / Date Soc Classification level # Nokia Siemens NetworksSMSCMSCBSCBTSBTSBTSBTSLA - 1LA - 2A - InterfaceLAPD (Abis) InterfaceMSMSAir - InterfaceMajor Issues that affect Paging PerformanceBCSU Processor Overload Lower/Upper Limit IssuesBSC Hardware UtilizationCell Reselection Strategy ( HYS - Specially in LA borders)Overshooting of Cells beyond the desired boundaryDistant & Un-necessary neighbor relationsPoor Coverage & QualityLAPD Load Against the Signaling Link Used ( 16/32/64Kbps)Paging Load ( High Page Volume) Above Capacity LimitsA Interface( SS7) Signaling LoadPage Time Out VLR Subscriber Capacity BHCA ( SMS & Voice)SMSC Capacity UtilizationPage Time OutPaging Deletion in CellsRACH Collisions OverloadOther than Capacity Issues, PAGE TIME OUT is the main reason that is to be analyzedExample of smart Network --PhilippinesSoc Classification level # Nokia Siemens NetworksSoc Classification level # Nokia Siemens Networks27Config Assement==============Performed prior to Parameter AssesmentTo Evaluate Features & Setting , Frequency Utilizations, TCH/GPRS Config, Node capacity Utilizations.

Paging Scenario in SMART TMSI is used for both INITIAL PAGING & PAGE REPETITIONRe-page Interval ( INT3.5 Sec ) Re-Paging Attempts is 1 ( PAGE IS REPEATED ONCE)TMSI Re-Allocation is not done during MT Call & MT SMS Conclusion

Soc Classification level # Nokia Siemens NetworksSoc Classification level # Nokia Siemens Networks28Config Assement==============Performed prior to Parameter AssesmentTo Evaluate Features & Setting , Frequency Utilizations, TCH/GPRS Config, Node capacity Utilizations.

SMS Assessment No Page Response

Detailed analysis of Trace is in next slidexClear Code 12 (NO PAGE RESPONSE) - ReasonsPaging time outSubscriber is not reachableNo response to paging message

Network Element Capacity & Interface Analysis - SMSC

Possible reasons Mobile Station Reason MS does not give the response to the paging message Network Availability Issues Out of Coverage Area During Location Update Process / LU Update Failure



B-Subscriber is in Same BSC ( In this case BSC48)

Indicates need to increase INT ( Re-page Interval) as MS took long time to RESPONDNetwork Element Capacity & Interface Analysis - SMSC

DX Cause 0x12 indicates NO PAGE RESPONSE ( Or Page Failure). MS in same location User A sends SMS to User B

NO PAGE RESPONSE to 1st Attempt Including, REPAGE ( Time Out after 7 Sec) PAGE SUCCESFUL in 2nd RETRY , but 5.66 Sec Page Response time MT SMS to Same CustomerBut Took 2 RETRYTime Out after 7 SecSoc Classification level # Nokia Siemens NetworksSoc Classification level # Nokia Siemens Networks30Config Assement==============Performed prior to Parameter AssesmentTo Evaluate Features & Setting , Frequency Utilizations, TCH/GPRS Config, Node capacity Utilizations.


B-Subscriber switches between 2 BSC

Finding from Trace file :B Subscriber switches between 2 LACs. When the subscriber was paged 1st time, the MS may be under location update process & NO PAGE RESPONSEAgain after 2 min 46 Sec , the customer was again Paged with new LAC / Cell IDPage was Successful, again the response time was 4.02 Sec.

Main ObservationsLocation update and/or Cell Reselection process took more time. Observed high setting of Cell Reselect HysteresisHowever its evident that the Page Response time is high as 4.02 Sec, After 1st SMS delivery attempt failed.In SMART the Page Response Timer ( INT- Re Page Interval) is set at 3.5 Sec.

1. Need to increase Re- Page interval from 3.5 Sec 4.5 Sec2. Review Cell Reselect Hysteresis (HYS) in Cells at LAC border. Example in later slides ( Slide 22)Network Element Capacity & Interface Analysis - SMSC


Paging Success Rate Snapshot Source: VLR measurement report, paging per LAC (353/161H), 30 Jun 09 21:00Average Paging Success Rate is less than 85% in LACs of MSCG11Page Volume is quite high across all LACs when compared to No of Cells in LAC ( LA Size)Snapshot of this in the following slide.Soc Classification level # Nokia Siemens NetworksSoc Classification level # Nokia Siemens Networks32Config Assement==============Performed prior to Parameter AssesmentTo Evaluate Features & Setting , Frequency Utilizations, TCH/GPRS Config, Node capacity Utilizations.

LAPD ANALYSISPaging Presentation / Author / Date

Soc Classification level # Nokia Siemens NetworksA Interface Signaling Link Load ( MSC BSC)

All of Signaling links towards BSCs (BSC1148 and BSC145) are overload during busy hour. The average are 0.34 Erlang since before and after new promotion. NSN recommended Value is 0.2 Erlang.Recommended to change few VLR/PLMN Parameters to reduce the Signaling Load. Ref: Next SlideNetwork Element Capacity & Interface Analysis - MSC


Cell Overshooting, beyond the expected Increased number of Adjacency in other LAC ( As a result of more LACs)Network Element Capacity & Interface Analysis BTS & Air InterfaceExample Case of Cell SH08FTPNR3 is shown in next slide

Cell SH08FTPNR3 which is in LAC border , Overshoots to 3.8Km reaching the 2nd neighboring LACThis Cell has high RACH deletions and considerable Page DeletionsSoc Classification level # Nokia Siemens NetworksSoc Classification level # Nokia Siemens Networks35Config Assement==============Performed prior to Parameter AssesmentTo Evaluate Features & Setting , Frequency Utilizations, TCH/GPRS Config, Node capacity Utilizations.

ND Report--Paging Deletion--186Presentation / Author / Date

Soc Classification level # Nokia Siemens NetworksCell having AG DeletionND 202Presentation / Author / Date

Soc Classification level # Nokia Siemens NetworksBCSU LOADND 184Presentation / Author / Date

Soc Classification level # Nokia Siemens NetworksSummary of Recommendations for Improving Paging PerformanceMaintain the A Interface (SS7) signaling load below 0.2 Erls ( Currently its above 0.34 Erls) Traffic Migration from MSCG11 to other MSC to reduce the Traffic Load.Remove INACTIVE BSCs ( definition) from MSCs . ( MSCG11 has only 2 BSCs where defined are 7)Monitor & maintain BCSU Load in safe limits Less than 60% Average LoadReduce the number LACs ( Combine LAC if Page load is less) Paging Load ( LAPD limits).Minimum 32Kbps LAPD signaling is to be used. If LAPD Overload Alarm(2133) is present in few Cells, increase to 64KbpsImplement the Layering Analysis & Recommendation from NSN.

NSN Recommendation to maintain good Paging Success RateOnce Paging Success Rate is improved after implementing the recommendations in previous slide, followingactivities has to be done or monitored to maintain Good Paging Success RateSoc Classification level # Nokia Siemens NetworksSoc Classification level # Nokia Siemens Networks39Config Assement==============Performed prior to Parameter AssesmentTo Evaluate Features & Setting , Frequency Utilizations, TCH/GPRS Config, Node capacity Utilizations.

Paging OptimisationPaging is a procedure in which the PLMN attempts to reach a mobile subscriber within the location area in which the subscriber is currently registered. In a mobile-terminated call, the MSC/VLR sends a paging order to the BSCs /RNCs controlling the last location area of the mobile station. To be able to do this, the MSC/MSS has to know which BTSs belong to which location areas and by which BSCs/RNCs they are controlled. Paging can be done either with the TMSI or IMSI of the mobile station. The network operator can define if paging will be repeated in the case in which the first paging is done with TMSI or IMSI and the MS is not found. If the paging is repeated, it is done with the IMSI. The paging retry mechanism consists of two levels. On the one hand, the Visitor Location Register (VLR) requests the paging first with the Temporary Mobile Subscriber Identity (TMSI) and when there is no response, it can request the paging with the subscriber's International Mobile Subscriber Identity (IMSI). On the other hand, the Mobile Services Switching Centre (MSC) can repeat the paging over the A/Iu interface several times with the actual TMSI or IMSI. Soc Classification level # Nokia Siemens NetworksIMSI paging

Successful PagingWith IMSISoc Classification level # Nokia Siemens NetworksRe-paging

Unsuccessful PagingWith IMSISoc Classification level # Nokia Siemens NetworksPower ControlSoc Classification level # Nokia Siemens NetworksSoc Classification level # Nokia Siemens NetworksPower Control StrategyTriggeringthresholdActual average samplesNx samplesLess than Px samples exceed thresholdNo power change triggeredNx samplesPx samples exceed thresholdPower change triggeredSignal level thresholds

pcUpperThresholdLevelDL/UL-110..-47 dBmpcLowerThresholdLevelDL/UL-110..-47 dBm

Signal quality thresholds

pcUpperThresholdQualDL/UL0..7pcLowerThresholdQualDL/UL0..7

Number of average samples

Nx1..32Px1..32Power change step size estimationSoc Classification level # Nokia Siemens NetworksPower Control StrategyScenariosExceeded thresholdActionReason

pcUpperThresholdLevelDLBTS power decreaseSignal levelpcLowerThresholdLevelDLBTS power increaseSignal levelpcUpperThresholdLevelULMS power decreaseSignal levelpcLowerThresholdLevelULMS power increaseSignal level

pcUpperThresholdQualDLBTS power decreaseSignal qualitypcLowerThresholdQualDLBTS power increaseSignal qualitypcUpperThresholdQualULMS power decreaseSignal qualitypcLowerThresholdQualULMS power increaseSignal qualitySoc Classification level # Nokia Siemens NetworksHandover Control and AdjacenciesSoc Classification level # Nokia Siemens NetworksSoc Classification level # Nokia Siemens NetworksIntra cell hoPresentation / Author / Date

Soc Classification level # Nokia Siemens NetworksPresentation / Author / Date

INTRA BSC HOSoc Classification level # Nokia Siemens NetworksPresentation / Author / Date

INTER BSC HO OR INTRA MSC HOSoc Classification level # Nokia Siemens NetworksSynchronized Handover SignallingNew Channel, New CellACTIVE CALL

HANDO CMD

HANDO ACCHANDO ACCHANDO ACCHANDO ACC

HANDO COM

ACTIVE CALLMSNETWORKOld Channel, Old CellOriginal and target cells controlled by same BCFNo timing advanced information required for MS

Inter cell handover from one sector to another of same BTSSoc Classification level # Nokia Siemens NetworksHandover StrategyTriggeringthresholdActual average samplesNx samplesLess than Px samples exceed thresholdNo handover triggeredNx samplesPx samples exceed thresholdhandover triggeredSignal interference thresholdshoThresholdsInterferenceDL/UL-110..-47 dBm

Signal quality thresholdshoThresholdsQualDL/UL0..7

Signal level thresholdshoThresholdLevelDL/UL-110..-47 dBmhoThresholdRapidLevelUL-110..-47 dBm

MS speed thresholdsupper/lowerSpeedLimit0..255 (unit = 2km/h)

Number of average samplesNx1..32Px1..32Target cell selectionSoc Classification level # Nokia Siemens NetworksHandover Strategy(Handover Reasons)

Timing AdvanceAdjacent CellsDownlink QualityUplink QualityAV_RXQUAL_UL_HOAV_RXQUAL_DL_HODownlink LevelUplink LevelAV_RXLEV_UL_HOAV_RXLEV_DL_HOAV_RANGE_HOAV_RXLEV_NCELL(n)INTERFERENCE &QUALITYLEVELDISTANCEPERIODICRX LEVELCHECKUMBRELLAPOWER BUDGETIMPERATIVE HOCHANNEL ADMINISTRATIONDIRECTED RETRYTHRESHOLD COMPARISONRAPID FIELD DROPMS SPEEDMS SpeedAV_MS_SPEEDOthers causes (NO TRESHOLD COMPARISON)- Intelligent Underlay/Overlay (IUO)- Traffic Reason Handover (TRHO)- Direct Access to Desired Layer/Band (DADL/B)Soc Classification level # Nokia Siemens NetworksHandover Strategy(Standard Target Cell Ranking)Cellabc

Overloaded?N/YNNPriority433 hoLoadFactor211Corrected priority4/233Rx level-75-80-83

No cell overloaded -> priorities 4,3,3 -> cell list a,b,cA overloaded-> priorities 2,3,3 -> cell list b,c,aAdjacent Cell Load Threshold Can be checked only for cells belonging to the same BSC as the serving onebtsLoadThreshold0..100 %

Adjacent Cell PriorityhoPriorityLevel0..7

Overloaded Cell -> Reduction of PriorityhoLoadFactor0..7

Ranking (not for imperative and traffic reason handover)1) Corrected priority2) Cells with same priority -> RX levelSoc Classification level # Nokia Siemens NetworksHandover Strategy(Decision due to RX level)AV_RXLEV_NCELL(n) > rxLevMinCell(n) + Max (0, msTxPwrMax(n) P)P depends on MS power class1aAny kind of handover (except umbrella)AV_RXLEV_NCELL(n) > hoLevelUmbrella(n)1bUmbrella handoverMinimum allowed signal level for target cell

rxLevMinCell-110..-47 dBmany handover (except umbrella)hoLevelUmbrella-110..-47 dBmumbrella handoverSoc Classification level # Nokia Siemens NetworksPBGT = (msTxPwrMax - msTxPwrMax(n)) (AV_RXLEV_DL_HO - AV_RXLEV_NCELL(n)) - (btsTxPwrMax - BTS_TXPWR)PBGT = (33dBm - 33dBm) - (-90 - (-80)) - (42dBm - 42dBm) = 10 dB > 6 dBPBGT > hoMarginPBGT(n) fulfilledAV_RXLEV_NCELL(n) > rxLevMinCell(n) + Max (0, msTxPwrMax(n) - msTxPwrMax)-80 dBm > -99 dBm + (33 dBm - 33 dBm) = -99 dBm fulfilled1a2aAV_RXLEV_DL_HO = -90 dBmmsTxPwrMax = 33 dBmBTS_TX_PWR = 42 dBmbtsTxPwrMax = 42 dBmServing Cell:Best Adjacent Cell:AV_RXLEV_NCELL(n) = -80 dBmrxLevMinCell(n) = -99 dBmmsTxPwrMax(n) = 33 dBmbtsTxPwrMax = 42 dBmhoMarginPBGT(n) = 6 dBPower Budget Handover(Example)Soc Classification level # Nokia Siemens NetworksPARAMTERS & EFFECTSPresentation / Author / Date Soc Classification level # Nokia Siemens NetworksRECOMMENDATION PARAMTERS 2G RadioSoc Classification level # Nokia Siemens NetworksSoc Classification level # Nokia Siemens NetworksBTS PARAMETERSHOC PARAMETERS

Soc Classification level # Nokia Siemens Networks

POC PARAMETERS

ADCE PARAMETERSSoc Classification level # Nokia Siemens NetworksBSC PARAMETERS

Soc Classification level # Nokia Siemens Networks73 2006 Nokia 1. Network Optimization Principles / 2006-08-11Default parametersBSC, BTS, HOC, POC, ADCE, TRX tables

Sensitive parametersBTS table: HOP, BAR, PLMN, ACC, RXP, TLC, PMAX, DMAX, TRP, IDLE, ACT, RDIVPOC table: PMAX, UDR, UUR, LDR, LUDHOC table: EPB, HPP, LDWS, LUWS, QDWS, QUWS, QDR, QDP, QDN, QUR, QUP, QUN, LDR, LDP, LDN, LUR, LUP, LUN, ADCE table: PMRG, LMRG, QMRG, MRGS

Specific parametersBTS table: BSC id, BCF id, SEG id, BTS id, BTS NAME, Cell id, MCC, MNC, LAC, RAC, NCC, BCC, MAL, HSN1, HSN2, MO, MS, CDEF, CDEDADCE table: BSC id, BTS id, N-LAC, N-Cell id, N-BCCH, N-NCC, N-BCC, synchronisedTRX table: BSC id, BTS id, TRX id, FREQ, TSC, TSL configuration

Default, Specific and Sensitive ParametersSoc Classification level # Nokia Siemens NetworksBTS Table:HOP - btsIsHoppingBAR - cellBarredPLMN plmn-permittedACC - notAllowedAccessClassRXP - rxLevAccessMinTLC - timeLimitCallPMAX - msTxPwrMaxDMAX - msMaxDistanceInCallSetupTRP - trxPriorityIntsAllocIDLE - idleStateBCCHAllocationACT- measurementBCCHAllocationRDIV diversityUsed

POC Table:PMAX bsTxPowerMaxUDR pcUpperThresholdLevDLUUR - pcUpperThresholdLevULLDR - pcLowerThresholdLevDLLUR pcLowerThresholdLevUL

HoEPB - enablePwrBudgetHandoverHPPhoPeriodPBGTLDWShoAveragingLevDL / windows sizeLUWShoAveragingLevUL / windows sizeQDWShoAveragingQualDL / windows sizeQUWShoAveragingQualUL / windows sizeQDRhoThresholdsQualDL / rxqualQDPhoThresholdsQualDL / pxQDNhoThresholdsQualDL / nxQURhoThresholdsQualUL / rxqualQUPhoThresholdsQualUL / pxQUNhoThresholdsQualUL / nxLDRhoThresholdsLevDL / rxlevLDPhoThresholdsLevDL / pxLDNhoThresholdsLevDL / nxLURhoThresholdsLevUL / rxlevLUPhoThresholdsLevUL / pxLUNhoThresholdsLevUL / nx

PMRG - hoMarginPBGT(n)LMRG - hoMarginLev(n)QMRG - hoMarginQual(n)MRGS - enableHoMarginLevQual(n)

DRTdrThreshold(n)ACLAdjacentCellLayer(n)

74 2006 Nokia 1. Network Optimization Principles / 2006-08-11Synchronised handoverSite BSite ANon-synchronised HandoverMS sends access bursts (HO_ACCESS) (with varying TA) until it receives PHYSICAL_INFOSynchronised HandoverMS sends a few access bursts (HO_ACCESS) and then starts transmission with previous TA

Non-synchronised handover leads to a longer communication interruption than synchronised handover (200ms vs. 100ms)Synchronized HO should be activated between sectors of the same site. If activated on inter-site adjacencies the handover can fail

Synchronized HONon- Synchronized HOSoc Classification level # Nokia Siemens NetworksSynchronous HO: the MS is able to compute the new timing advance (to be applied with BTS-new), because old and new BTSes are synchronized.Asynchronous HO: the time advance must be initialized at the MS and at the BTS-new during the HO procedure.Time advance: to avoid propagation delays problems MS advances its emission relatively to its reception by a time compensating the to and from propagation delay. The BTS provides this value to the MS.

Which HO type is really used: synchronized on unsynchronized HO? How is the synchronization between BTSes get for the synchronized HO?Synchronized HOs are used in co-located cells within the same BCF (same master clock, and timing for all the cells)When handovers are performed between different sectors of one site the handovers are normally synchronized because the equipment are normally located in one premises and can therefore be synchronised with each other. To synchronize different cabinets there is a synchronisation cable between the cabinets. Note that if the network is a synchronized network (Nokia feature that is based on providing a master clock to different BTSs with GPS connection) the handovers are not synchronized since the synchronized HO needs requires that there is no timing advance difference between the different cells.

Same site above actually means "same BCF".Generally don't use synchronised handover with repeaters, but in some cases it could workSlide above is not very precise! The TA of Access Bursts is constant. The TA is assessed based on the delay of burst arrival.It may be better to play it safe, and make all Handovers non-synchronised. Small degradation in performance, but we don't risk anything.

75 2006 Nokia 1. Network Optimization Principles / 2006-08-11Examples of wrong parameter set with impact on network operation/performance call setup, qual, bandsNo calls happening in a cellCell BarredNon existent (LAC, Cell ID) in MSCDMAX = 0

Very few calls happening in a cellRxLevAccesMinWrong MNC, MCC, LAC declaration

Very low traffic in a cellmsTxPwrMax = 0, bsTxPwrMax = 30

Bad quality in UL after rehoming

Few traffic in 1800 layer of a dual band 900/1800 networkSoc Classification level # Nokia Siemens Networks76 2006 Nokia 1. Network Optimization Principles / 2006-08-11Example 1a

HandoverCall SetupSYS INFO 3 (BCCH)(CellBarrAccess = yes)No calls happening in a cell: The cell has been barred

Soc Classification level # Nokia Siemens NetworksCell Barred is a sensitive parameter and can avoid any calls to happen in the cell. (Default value = N - ok)

Cell Barr Access bit is sent over the BCCH in the RACH Control Parameter IE in the SYSTEM INFORMATION 3 message. When MS selects a cell where Cell Barr Access bit is set to 1, MS is forbidden to send any CHANNEL REQUEST. Thus, calls are not possible. Nevertheless, incoming handovers remain possible.

cell barred (BAR)GSM reference:I-ETS 300 022-1 (GSM 04.08)Q3 name:cellBarredModification:OnlineRange:Y/NMML default:NDescription:With this parameter you define whether MSs are allowed to access the cell.Related command(s):EQF, EQO77 2006 Nokia 1. Network Optimization Principles / 2006-08-11Example 1b

MSC does not find (LAC, CI) in its databaseNo calls happening in a cell: CI different between MSC and BSC or non existent (LAC, Cell ID) in MSCSoc Classification level # Nokia Siemens NetworksActivate parameters in MSC!

(LAC, CI) towards which the MS has sent a RACH are informed to the MSC via the CR message. BSC has already reserved SDCCH channel for the air interface and is waiting for confirmation from MSC (CC message). If (LAC, CI) has not been created properly in MSC, it generates alarm in MSC and SDCCH failure in BSC whose direct effect on the end-user is a call setup failure.78 2006 Nokia 1. Network Optimization Principles / 2006-08-11Example 1cNo calls happening in a cell:MsMaxDistanceInCallSetup (DMAX) = 0

DMAX = 0

RxLevel = -70 dBmCall SetupDespite the coverage of the cell, no calls will be established!Soc Classification level # Nokia Siemens NetworksIf no calls are happening on the cell, verify if value of sensitive parameter DMAX = 0. ( Default value = 255 - ok)When used, DMAX must be used with care as islands of coverage can be formed.

MS max distance in call setup (DMAX)GSM reference:No ref.Q3 name:msMaxDistanceInCallSetupModification:OnlineRange:0..255MML default:255

Description:With this parameter you define the maximum distance between the BTS and the MS in call setup. The maximum distance is expressed as an access delay. Within the range of 0...62, one step correlates to a distance of 550 meters. If the access delay of the channel request message exceeds the given maximum, the call attempt is rejected. When the parameter is given a value from 63 to 255, call attempts are never rejected.

Related command(s):EQM, EQO

Note:The option DISTANCE_VERIFYING needs to be enabled in order for this parameter to be functional.79 2006 Nokia 1. Network Optimization Principles / 2006-08-11Example 2bVery few calls happening in a cell: Wrong MNC, MCC, LAC declaration in network - MNC: 01 1 !!! (In OSS correct value)

Soc Classification level # Nokia Siemens Networks80 2006 Nokia 1. Network Optimization Principles / 2006-08-11Example 3bsTxPwrMax 0 30 dB 0 dBbsTxPwrMin 0 30 dB 30 dBminMsTxPower0 36 dBm 0 dBmsTxPwrMax0 36 dBmParameter Value_______Default value BTS Max Power = BTS Power (bsTxPwrMax = 0 dB)BTS Min Power = BTS Power (bsTxPwrMin = 30 dB)Attenuation Values (dB)Power Values (dBm)

MS Max Power = (msTxPwrMax = 33 dB)MS Min Power = (minMsTxPower = 13 dB)

Absolute DeltaVery low traffic in a cell: msTxPwrMax = 0, bsTxPwrMax = 30

Soc Classification level # Nokia Siemens NetworksThese are tricky parameters! Careful not to make confusion: BTS parameters are related to Attenuation Values, while MS parameters are directly the Absolute Power Values! (Default values in table - ok)

Although msTxPwrMax can be set to 0, this will not permit the MS to reach the BTS!bsTxPwrMax set to 30 means that the maximum power of the BTS will have a very high attenuation of 30 dB! So if the user changes the meaning of these BTS and MS power control parameter no calls will be established in the network.

BTS Max Power = BTS Power (bsTxPwrMax = 0 dB)Maximum power has 0 dB of attenuation

BTS Min Power = BTS Power (bsTxPwrMin = 30 dB)Minimum power has 30 dB of attenuation

BS TX pwr max (PMAX1)GSM reference:I-ETS 300 033 (GSM 05.05)I-ETS 300 034-1 (GSM 05.08)Q3 name:bsTxPwrMaxModification:OnlineRange:0..30 (dB) with a step size of 2MML default:0Description:With this parameter you identify the maximum transmission power of the BTS as an attenuation from the peak power of the TRX. This parameter is used for frequency bands GSM 800 and GSM 900.Related command(s):EUC, EUG, EUONote:There are limitations for Nokia InSite.

BS TX pwr min (PMIN)GSM reference:I-ETS 300 033 (GSM 05.05)I-ETS 300 034-1 (GSM 05.08)Q3 name:bsTxPwrMinModification:OnlineRange:0..30 (dB) with a step size of 2MML default:30Description:With this parameter you identify the minimum transmission power of the BTS as an attenuation from the peak power of the TRX.Related command(s):EUC, EUG, EUONote:There are limitations for Nokia InSite.

MS txpwr min (PMIN)GSM reference:No ref.Q3 name:minMSTxPowerModification:OnlineRange:GSM 900 and GSM 800: 5..39 (dBm), with step size of 2GSM 1800: 0..36 (dBm), with step size of 2GSM 1900: 0..32 (dBm), with step size of 2, and 33 (dBm)MML default:GSM 900 and GSM 800: 5GSM 1800: 0GSM 1900: 0Description:With this parameter you define the minimum power level an MS may use in the serving cell.Related command(s):EQM, EQO

81 2006 Nokia 1. Network Optimization Principles / 2006-08-11Example 4Bad quality in UL after rehoming: DiversityUsed parameter not set to yes anymore

RDIV = Y

Uplink Diversity improves quality of signal received. After rehoming RDIV parameter was set to default value (No) and UL quality was affected.Soc Classification level # Nokia Siemens NetworksRecommended value = YES while default value = NO!Always verify the network status BEFORE and AFTER any modification in the network. After rehoming RDIV parameter was set to no and UL quality was affected. Also, not all neighbours were recreated!

RX diversity (RDIV)GSM reference:No ref.Q3 name:diversityUsedModification:OnlineRange:Y (RX diversity is used)N (RX diversity is not used)MML default:NDescription:With this parameter you define whether RX diversity is used in the BTS.Related command(s):EQM, EQONote:The parameter is only allowed for Nokia MetroSite and Nokia UltraSite.82 2006 Nokia 1. Network Optimization Principles / 2006-08-11Example 5Few traffic in 1800 layer of a dual band 900/1800 network:Idle Mode: C2 parameters not set properly (temporaryOffset, penaltyTime)BCCHBCCHfast moving mobileslow moving mobile1800: micro-Layer900: macro-layer

Soc Classification level # Nokia Siemens NetworksAdjust C2 parameters in order to guarantee traffic balance between layers. Verify also umbrella HO parameters in dedicated mode.

In case temporaryOffset or penaltyTime is set to a very high value, micro-layer might not be re-selected and call setups will not happen to this layer.

C1 + cellReselectOffset - temporaryOffset*H(penaltyTime-T) = 300)spare057044 /c57044 (S10.5)drop_after_TCH_assign c1202 (S11)drops after this pointcsf_15csf_13Dcr_8eSoc Classification level # Nokia Siemens NetworksTCH DROP-ND REPORT(163)Presentation / Author / Date

Soc Classification level # Nokia Siemens NetworksTCH DROPKPI REPORTPresentation / Author / Date

Soc Classification level # Nokia Siemens NetworksKPI- Rules, TCH Drop

Soc Classification level # Nokia Siemens NetworksKPI- Rules, TCH Drop (RF)

Soc Classification level # Nokia Siemens NetworksKPI- Rules, TCH Drop (abis)

Soc Classification level # Nokia Siemens NetworksKPI- Rules, TCH Drop (A)

Soc Classification level # Nokia Siemens NetworksKPI- Rules, TCH Drop (TR)

Soc Classification level # Nokia Siemens NetworksKPI- Rules, TCH Drop (Other)

Soc Classification level # Nokia Siemens NetworksTCH Drop and Corrective actionNon RF drops : Check the TCH drop reason in BBH stats report. Non RF drops may have two reasons one is TR drop and other A-bis fail . If you find such issues in a site/cell then escalate to O&M team and do continuous follow up till the same got corrected. Hint : If all cells or a single cell in a site is having TR drops then check the PCM mapping and the link stability . If most of the cells /sites in a BSC is having TR drops High then escalate the same to OMC to check TRAU block . For A-bis drop, it is the link or the E1/T1 card which may have issues or any issue in the internal wiring of the BTS .

RF Drops : 1. If RF drop is high in cells first step is to check the Air interface clearance (BCCH reuse pattern and C/I, and the database for Hopping, Over shooting sites, neighbour missing and neighbour definitions , call dragging due to congestion in neighbour cells, border cells, VSWR issues or TRX wrong connections). Try to minimize the Overlapping to reduce the co channel hitting and quick HO attempts .

Corrective action : See the path balance reports (208) to find out the VSWR issues , see to the assignment issues in those cells, analyze the neighbour cells resource availability during BBH to take the HO request , Look into the BCCH reuse in the coverage area of the cell , check the overshooting of the cell to longer distances and try to reduce the same thro optimization, check the Hopping pool MA List and MAIO and try to have best offset to avoid co.and adj. interference.Check Fractional Frequency loading in the cell ,restrict over shooting cells( This can be checked thro the report (196) which will give you a clear indication of bad samples and confirms if all TRXs are having bad samples during BBH ) . Soc Classification level # Nokia Siemens Networks2. Another reason for RF drop may be due to HW faults in BTS ,like TRX having poor quality TS , wrong antenna connections ,VSWR Issues in sites Corrective action : Check the assignment success rates in those cells where drop rate is high this will give you hint about the wrong connections of the devices ,Antennas . Look into the TRX Quality reports (196) where you can look into the poor quality samples per TRX if some TRX is having high poor UL/DL quality samples and others in the same cells are having good samples then the particular TRX is having some issue ,replace the same thro O&M team

3. Minimize the Hand Over attempts between cells by minimizing the overlapping of source and target cells and also setting the margins and Ping pong rejection timers .

4. Ensure the RLT and ARLT (in AMR environment ) is properly set guidelines we can set RLT 24 Frames and ARLT 36 Frames )

4. If all above you are finding ok still there is high RF drops then have a drive test and site audit to find out any external interference or Antenna issues in field ,check the VSWR thro O&M team . Following the procedures defined above and taking corrective action in time will result into a Quality network with Drop KPI maintained .

Soc Classification level # Nokia Siemens NetworksParameters & featuresPresentation / Author / Date B TS parameter :Antenna Hopping,;;DMAX,;;STIRC;;BFG

2. BSC parameter:ITCF 3. MSC parameter : Call Re establishment

4. Features : AMR PPC, ROBUST AMR

Soc Classification level # Nokia Siemens NetworksPresentation / Author / Date

Soc Classification level # Nokia Siemens NetworksKPI- Rules, HO fail

Soc Classification level # Nokia Siemens NetworksHO FAILURE REPORTND (153)Presentation / Author / Date

Soc Classification level # Nokia Siemens NetworksHANDOVER ANALYSIS Presentation / Author / Date

Soc Classification level # Nokia Siemens NetworksHO CAUSES BSC WISEPresentation / Author / Date

Soc Classification level # Nokia Siemens NetworksHO CAUSESCELL WISE--154Presentation / Author / Date

Soc Classification level # Nokia Siemens NetworksPOOR HOSR Look into the 153 report for HOSR between source and target cellsList all the neighbours where there is poor HOSR See the sites are performing well and there is no assignment failure issues and TRX HW issues Look into the BCCH and BSIC reuse pattern of the neighbours to ensure good C/I of the BCCH carrier and their definition in neighbour.Do the neighbour audit and check all the neighbours defined with proper database and LAC etc etc

Define Sync neighbours between cells in a single siteCheck the Signaling load on A-bis and A-terThro Neighbour audit remove all neighbours which are not with level to retain the call and add all missing neighbours. Check the HO parameters and margins ,rescue hand over settings ,penalty timers from ZEAO and ZEHO logs to ensure less attempts and enhnace the success rate Check the whether Clock shift DAC ( 1800-2400 )Check Software mis match( BSC and BTS end

Soc Classification level # Nokia Siemens NetworksIf AMR enabled ,NSS team should ensure Proper dimensioning and A-ter link availability for codecs in TRAU .

Optimize the Overlap areas between cells to have minimum HO requests in each call .Decongest the target cells to ensure TCH resource availability for a HO request .Try to introduce more Ho margin between cells inter BSC to have less attempts for Inter BSC HO .

Allow RX Lev HO between single sites and minimum overlapping neighbours , with a very less HO Margin and penalty timer In an AMR scenario to minimize the quality HO ensure the Threshold level for Quality HO is set RX qual 5 or 6 .

Poor HOSR Impact: Enhances TCH drop, TCH Block due to poor mobility management between sites.

Concentrating on reports and following the procedures defined above and taking corrective action in time will result into a Quality network with all KPIs maintained

Soc Classification level # Nokia Siemens NetworksParamters and features Presentation / Author / Date BTS Parameter : SL, PRI,PMRG,LMRG,QMRG,

HO parameter : MIU,MIH,HPP;;QDR & QUR;;LDR & LUR;;LAR & LER;C/I estimation method

BCF parameter : DAC drift

MSC : LAC Mismatch

AMR : IHRH & IHRF,SAL;;;n(x),p(x) change for QDRF & QURF

Soc Classification level # Nokia Siemens NetworksRX QUALITYPresentation / Author / Date 100* (sum of RxQual samples 0-5)/sum of all RxQual samples 0-7)

Soc Classification level # Nokia Siemens Networks173 2006 Nokia 1. Network Optimization Principles / 2006-08-11Rx Quality

DL/UL CUMULATIVE QUALITY < 5 (dlq_2/ ulq_2)

Network Doctor report 196 modelSoc Classification level # Nokia Siemens Networks174 2006 Nokia 1. Network Optimization Principles / 2006-08-11Rx Quality x Rx LevelDL/UL QUALITY/LEVEL DISTRIBUTION

Network Doctor report 204 model

Soc Classification level # Nokia Siemens Networks175 2006 Nokia 1. Network Optimization Principles / 2006-08-11Rx Quality x Rx Level

Coverage Problem: Bad quality and Low Rx LevelInterference Problem: Bad quality and High Rx LevelGood QualityHigh Rv LevelHW Problem:Bad Quality for all Rx LevelsNWD report 204 modelSoc Classification level # Nokia Siemens Networks176 2006 Nokia 1. Network Optimization Principles / 2006-08-11Coverage ProblemBad Quality is due to weak signal. Check TA statistics. Add sites.

Interference ProblemInternal interference. Check if interference profile follows increases in traffic profile. Check frequency plan and TA statistics. Modify frequency to verify if problem is solved.External interference. Check if interference is independent of traffic profile.Due to synchronisation problem. Synchronisation source set in BTS clock. Change to BSC.

HW ProblemBad quality in all RxLevel classes of ONE TRX. Check alarms to verify whether there is a badly functioning TRX. Fix hardware problem. Check antenna line. Swap frequency. If problem persists on the same TRX, fix HW problem.Bad quality in all RxLevel classes of TWO TRX. Verify combiner or common parts connected to both TRX.

Rx Quality x Rx LevelSoc Classification level # Nokia Siemens Networks177 2006 Nokia 1. Network Optimization Principles / 2006-08-11Timing Advance

Low share close:BTS might be so high that area bellow it does not receive any signalThey might be another dominant site High share far:May be causing Interference and drop call rate as traffic is captured in certain regions far from the BTS.High share close:Most calls are established near the BTSBTS may have indoor coverageNWD report 232 modelDecreasing share:Traffic is distributed mostly in regions with higher signal levelDont forget: Traffic distribution depends on clutter types and planned coverage!Repeters can change expected distribution.Soc Classification level # Nokia Siemens Networks178 2006 Nokia 1. Network Optimization Principles / 2006-08-11High share of traffic far from the BTS

Internal Interference Problem: High drop call rate in a certain area. Rx Quality statistics indicates an internal interference problem. With planning tool evaluate sites with the same frequency - interfering candidates. TA statistics will show traffic distance of interfering cells. Downtilt is needed.

No neighbours in area: High drop call rate. As this cell is covering na unexpected region, there will be no close neighbours declared and HO will not happen. Downtilt is needed.

Timing AdvanceSoc Classification level # Nokia Siemens NetworksPresentation / Author / Date

Soc Classification level # Nokia Siemens Networkserl / drop : amount of erlangs between two drops.It has no physical meaning, consider it as a tool. This is very very hard to visualize what it means...

High erl/drop : lot of traffic in the cell and little amount of call drops ---> Good cell

Low erlang / drop: that's where it gets complicated... it can mean two things:1./ very little amount of traffic and just a few call drops --> acceptable cell2./ high amount of traffic and VERY high amount of drops --> Very bad cell.

in my opinion, this is a useless indicator because you still need to check out other indicators to understand what it means, and how serious the problem is. For example, you need to check the number of call drops and the amount of erlangs

179ERLANG DROP PER MINPresentation / Author / Date

This KPI indicate the average time between the dropped calls. Its is a division of traffic expressed in minute Erlangs divided by the total drops and is inversely proportional to DCR.Soc Classification level # Nokia Siemens Networks180Congestion & blockingBTSTRXRACHBSCRACH/NOISE COLLISIONAbis link Alarm 2720 Telecom Link overload(030)SDCCH congestion time (130,216) c2033 = sdcch_cong_timeBlocked SDCCH seiz att (216) c1001 = sdcch_busy_attBlocking (204,204, 130,216) , csf_1aAif TCProcessor unitload (605,614)avg.70% critical(avg. 50% for MB)HLRTCH congestion time (138, 216), c2027 = tch_cong_timeBlocked TCH call att (216) blck_9cBlocking (204,200,138,216) , csf_3m,csf_3i,csf_3lNo direct counter butaffects csf_2j(200, 204, 250)Aif Circuit group blocking (602,604)M058, M026: Max. 1% in BHSignalling link (SS7) traffic(524)Add link if traffic > 200mErlNOTE: In MSC terminologyinstead of term blockingthere is term call congestion'RACH loadrach_3, rach_4(188, 216)MSPagingAG blocking (229,204, 200, 216) (blck_13)

AG blocking, GPRS (229) (blck_21)Access grantMSCProcessor unitload (184,212)avg.70% critical avg.60% max. is recommended by R&D (avg. 50% for MB)Processor unitload (606,615)avg.70% critical(avg. 50% for MB)Paging buffer occupancypagings deleted (186)SGSNBearer channel /NSVC (240)

Alarm '7746' Ch congestion in BTS above defined threshold'NOTE:The lines indicate logical source of the info,the actual genereation of the info can be in the abovestanding object500627 AIV PAGING REFUSED BIG LOAD (BSCU overload )0026 SIGNALLING LINK LOAD OVER THRESHOLD (>0.2erl)3164 PCU PROCESSOR OVERLOAD Soc Classification level # Nokia Siemens NetworksALARM ANALYSISAlarm NumberDescription7745CHANNEL FAILURE RATE ALARM2992BtTS and Tc unsynchronization clear calls on a interface2993BTS andTC unsynchronization clear calls on abis interface7508RADIO TIMESLOT FAILURE IN TRX7600BCF FAULTY7601BCF OPERATION DEGRADED7603BTS FAULTY7604BTS Operation Degraded7606TRX FAULTY7617SEVERAL CALLS DROPPED DUE TO PROBLEM WITH TRANSCODER7704PCM FAILURE7705LAPD FAILURE7715CONTINUOUS RESTARTS OF BCF-TRX7725TRAFFIC CHANNEL ACTIVATION FAILURE7738BTS WITH NO TRANSACTIONS7743MEAN HOLDING TIME BELOW DEFINED THRESHOLD2955TRANSCODER CHANNEL FAILURE7746CH CONGESTION IN CELL ABOVE DEFINED THRESHOLD7767BCCH MISSING7939FORWARD POWER TOO LOW AT TX ANTENNA8112FREQUENCY ERRORPresentation / Author / Date Soc Classification level # Nokia Siemens Networks7755Channel failure rate above defined Threshold

Presentation / Author / Date

Soc Classification level # Nokia Siemens Networks7745Presentation / Author / Date



Soc Classification level # Nokia Siemens Networks7601-BCF OPERATION DEGRADEDPresentation / Author / Date BCF Operation Degraded :This alarm 7601 is generated at the BTS.

BD018 BCF-0030 EQUIPM 2007-07-24 04:20:45.42 ** ALARM (14652) 7601 BCF OPERATION DEGRADED Difference between PCM and base station frequency reference. 02 01 07 96 00 00 1) Fault reason: Cabinet I2C bus is jammed.Solution:Switch the site power Off and On.Check the fan unit, the power supply unit and the TRXs. If necessary, replace the faulty units(s).If the fault reappears, replace the cabinet. The units inside the cabinet can be reused in the new cabinet2) Fault reason: Incompatible unit presence has been detected in the BTS.Solution:Replace the high power or EDGE TRX(s) with normal type TRX(s) and reset the BCFOr, replace the normal type FAN and power supply with high power or EDGE units. Now EDGE and high power TRXs are supported.Soc Classification level # Nokia Siemens Networks7601Presentation / Author / Date 3) Fault reason: Difference between the PCM and BTS frequency reference.Solution:Check the synchronisation settings of the transmission interface.( DAC Value)DAC value Range from 1800 t0 2200.If the settings are OK, check the transmission chain.If the alarm stays active or reappears after the recovery actions above, reset the BCF.If the alarm reappears after the BCF reset, replace the BTS.Note: If this Supplementary alarm appears there is Drift in clock value(DAC). That leads to HO failures4) Fault reason: Oven oscillator control is close to its margins. The oven might be outdated.Solution:Check the synchronisation settings of the transmission interface.If the settings are OK, check the transmission chain.If the alarm stays active or reappears after the recovery actions above, reset the BCF.If the alarm reappears after the BCF reset, replace the BTSNote: If this Supplementary alarm appears there is Drift in clock value (DAC). That leads to HO failures5) Fault reason: Flash operation failed in BOI or TRX.Solution:Replace the BOI (Base station operation Interface unit)If it is TRX change the TRXDescrpition of Supplementary information:1-6 XX XX XX XX XX XX 1 2 3 4 5 6 1 Rack (cabinet) number 2 shelf number3 slot4 Type of unit5 unit number6 subunit numberSoc Classification level # Nokia Siemens NetworksTHANK YOUSoc Classification level # Nokia Siemens NetworksSoc Classification level # Nokia Siemens NetworksBSC paramsome BSC parametersRangeFeature nameFeatureDefault NokiaDefault MacroChangesDMACdcsMacrocellThreshold0..36 (dBm) / 2 dB stepb2634DMICdcsMicrocellThreshold0..36 (dBm) / 2 dB stepb2432NPCGenHandoverReqMessageNoOfPrefCells1..16b33GMACgsmMacrocellThreshold5..43 (dBm) / 2 dB stepb3535GMICgsmMicrocellThreshold5..43 (dBm) / 2 dB stepb3333HDLHoPreferenceOrderInterfDLINTER, INTRAbINTERINTERHULHoPreferenceOrderInterfULINTER, INTRAbINTERINTRADISBMsDistanceBehaviour0..60 (s), 255b255255RXBALRxLevBalance0..20 (dB)b55DINHODisableIntHoY/NbNNVDLSVariableDLStepUseY/NbNNGTUGTTerrUpdateGuardTimeGPRS0..255 sGb interface fuctionalityo56DEXDRdisableExtDrY/NDirected RetryoNNALTAmhLowerLoadThreshold0..100%AMHo2020AMLAmhMaxLoadOfTgtCell0..100%AMHo7070AUTAmhUpperLoadThreshold0..100%AMHo8080TGTAmhTRHOGuardTime0..120 sAMHo3030BQLBadQualityLimit0..100%Dynamic HotSpoto100100GQLGoodQualityLimit0..100%Dynamic HotSpoto100100SQL1SigQualLimit10..100%Dynamic HotSpoto100100SQL2SigQualLimit20..100%Dynamic HotSpoto100100TCP1TchProbability10..100%Dynamic HotSpoto100100TCP2TchProbability20..100%Dynamic HotSpoto100100TCP3TchProbability30..100%Dynamic HotSpoto100100EPFPagingAnsOnFacchY/NFacch call setupoNNERFReestablishOnFacchY/NFacch call setupoNNEEFEmerCallOnFacchY/NFacch call setupoNNEOFOrdinaryCallOnFacchY/NFacch call setupoNNHRLBtsLoadDepTCHRate (Lower limit)0..100%Half Rateo100100HRUBtsLoadDepTCHRate (Upper limit)0..100%Half Rateo00HRITchRateInternalHo1..5Half Rate / Enhanced FullRateo11PRPieToSubscriber1..14Improved Trunk Reservationo--STSubscriberType0..2Improved Trunk Reservationo01

&A&LDefault Parameters / Telemar&C&D&R&P/&N

BCFNo radio Parameters related to BCF

BTS(ZEQO)BTS parameterRangeFeature nameFeatureDefault NokiaDefault MacroChangesmacro WLLmacro PCSBTSIDBTS-ID1..248b--xxNAMEBTS NAME15 characters--CIcell-ID0..65535b--xBANDfrequenceBandInUseGSM/DCS/DCS19b-DCSGSMbsIdentityCodeNCCNetwork Colour Code0..7b-01BCCBTS Colour Code0..7b--xxxlocationAreaIdMCCMobile Country Code0..999b-724604MNCMobile Network Code0..99 (0..999)(Three digit MNC)b (o)-311LACLocation Area Code0..65535b--xxxroutingAreaIdMCCMobile Country Code0..999b-724604MNCMobile Network Code0..99 (0..999)(Three digit MNC)b (o)-311LACLocation Area Code0..65535b--xxxRACRoutingAreaCode0..255Gb interface functionalityo--xxHierarchicalCellType-1HOPbtsIsHoppingN/BB/RFbNNRFMALusedMobileAllocation0..128b--x-xHSN1hoppingSequenceNumber10 (cyclic hopping) 1..63 (random hopping)b0-x0xHSN2hoppingSequenceNumber20 (cyclic hopping) 1..63 (random hopping)b0-x0-MOmaioOffset0..62b000MSMAIO step1..62Flexible MAIO Managemento1-2BARcellBarredY/NbNNREcallReestablishmentAllowedY/NbNNECemergencyCallRestrictedY/NbNNPLMNplmn-permitted0..7b-0..71ACCnotAllowedAccessClasses0..9, 11..15b--DRdrInUseY/NDirectedRetryoNNxYMIDRminTimeLimitDirectedRetry0..14 (s)Directed Retryo02x2MADRmaxTimeLimitDirectedRetry1..15 (s)Directed Retryo57x7DRMdrMethod0, 1Directed Retryo01x1HYScellReselectHysteresis0..14 (dB) / 2 dB stepb466TXPmsTxPwrMaxCCH0..30 (dBm) / 2 dB stepb303030RXPrxLevAccessMin-110..-47 (dBm)b-105-105x-102RLTradioLinkTimeout4..64 / 4 stepb202020POpowerOffset0..6 (dBm) / 2 dB stepb000MQLmaxQueueLength0..100 (%)b505050TLCtimeLimitCall0..15 (s)b1010x7TLHtimeLimitHandover0..10 (s)b522QPUqueuePriorityUsedY/NbYYYQPCqueueingPriorityCall1..14b101010QPHqueueingPriorityHandover1..14b988QPNqueuePriorityNonUrgentHo1..14b9109MPUmsPriorityUsedInQueueingY/NbYYYAGnoOfBlocksForAccessGrant0..7 (if combined BCCH not used)1..7 (if CBCH used at SDCCH/8)0..2 (if combined BCCH used)b11x0MFRnoOfMultiframesBetweenPaging2..9b24x4PERtimerPeriodicUpdateMS0, 0.1..25.5 (hours)b0.54x4ATTallowIMSIAttachDetachY/NbYYYcnThreshold0..63 (dB) (0=disabled)b00x0APinterferenceAveragingProcess1..32b666BO0boundary 0-110 (dBm) fixedb-110-110-110BO1boundary 1-110..-47 (dBm)b-105-105-105BO2boundary 2-110..-47 (dBm)b-100-100-100BO3boundary 3-110..-47 (dBm)b-95-95-95BO4boundary 4-110..-47 (dBm)b-90-90-90BO5boundary 5-47 (dBm) fixedb-47-47-47DTXdtxMode0 MS may use DTX1 MS shall use DTX2 MS shall not use DTXb211BMAbtsMeasAver1..4b111PMAXmsTxPwrMax0..36 (dBm) / 2 dB stepb303030PMINminMSTxPower0..36 (dBm) / 2 dB stepb01010RETmaxNumberRetransmission1, 2, 4, 7b44x4NY1maxNumberOfRepetition5..35b555SLOnumberOfSlotsSpreadTrans3..12, 14, 16, 20, 25, 32, 50b1010x25CBsmsCBUsedY/NbNYNBLTbtsLoadThreshold0..100 (%)b707070DMAXmsMaxDistanceInCallSetup0..62 (1 unit corresponds to 550 m) 63..255 (call attempts are never rejected)b25525520TRPtrxPriorityInTCHAlloc0, 1, 2,3b00x01CLCcellLoadForChannelSearch0..100b00NECInewEstablishCausesSupportY/NbNNNIDLEidleStateBCCHAllocation0 (BCCH frequency list is taken from the adjacent cells defined for the BTS)1...255 (identification of BCCH frequency list)Double BA Listso000ACTmeasurementBCCHAllocationADJ / IDLEDouble BA ListsoADJADJADJPIcellReselectionParamIndY/NC2 Cell ReselectionoNNxREOCellReselectOffset0..126 (dB) / 2 dB stepC2 Cell Reselectiono00x00TEOTemporaryOffset0..70 (dB) / 10 dB stepC2 Cell Reselectiono00x00TEOPenaltyTime20..640 (s)C2 Cell Reselectiono20202020QUACellBarQualifyY/NC2 Cell ReselectionoNNDBCMultiBandCellY/NDualBandoYYMBRmultiBandCellReporting0..3DualBando11ESIearlySendingIndicationY/NbYYIDRidrUsedY/NIntelligent Directed RetryoNNCTYcellTypeGSM/MCNIntelligent Directed RetryoGSMGSMCDEDdedicatedGPRSCapacity0..100 (%)Gb interface functionalityo00xCDEFdefaultGPRSCapacity1..100 (%)Gb interface functionalityo123xGENAgprsEnabledY/NGb interface functionalityoN1xBFGpreferBCCHfreqGPRSY/NGb interface functionalityoNNxHCLlowerLimitCellLoadHSCSD0..100 (%)High Speed Circuit Switched datao100100HCUupperLimitCellLoadHSCSD0..100 (%)High Speed Circuit Switched datao100100HDTdowngradeGuardTimeHSCSD0 (deactivated) 1..65535 (s)High Speed Circuit Switched datao00HMEminExhaustHSCSD1 (one TCH always released in downgrade) 2 (downgrade is made from four to two, three to two, two to one TCHs) 3 (downgrade is made from four to two, three to one, two to one TCHs) 4 (only one TCH left always after downgrade)High Speed Circuit Switched datao11HRCUupperLimitRegularLoadHSCSD0..100 (%)High Speed Circuit Switched datao100100HTMminHSCSDcapacityCell0..100 (%)High Speed Circuit Switched datao100100HUGupgradeGainHSCSD0 (no upgrade during guard time)33 (upgrade during guard time if gain at least 33%)55 (upgrade during guard time if gain at least 50%)100 (upgrade during guard time if gain at least 100%)High Speed Circuit Switched datao00HUTupgradeGuardTimeHSCSD0 (deactivated)1..65535 (s)High Speed Circuit Switched datao00TRtrunkReservationUsedY/NImproved Trunk ReservationoNNLIMITfreeTCHLimit1..16Improved Trunk Reservationo1616TCRPnbrTCHForPrioritySubs0..8Improved Trunk Reservationo00REMreservationMethodDYN / STATImproved Trunk ReservationoDYNDYNRUPpriorityChUseIncomingHOY/NImproved Trunk ReservationoYYTBLtableIdentification0..64Improved Trunk Reservationo--TTtrafficTypesForTrunk1 (GSM call setup)2 (MCN call setup)3 (GSM handover)4 (MCN handover)5 (priority call setup)6 (priority handover)7-10Improved Trunk Reservationo--FRLbtsSpLoadDepTCHRate0..100 (%)Half Rateo100100FRUbtsSpLoadDepTCHRate0..100 (%)Half Rateo00TRIHtchrateIntraCellHo0..4Half Rate or EFR Codeco00EXTradiusExtension0..35 (km)Improved solution for Extended cell radiuso00RDIVdiversityUsedY / W / NbNYSTRsoftBlockingStartReg0..255Dynamic Hot Spoto255255STSsoftBlockingStartSup0..255Dynamic Hot Spoto255255UHOPunderlayHoppingModeBB/RF/NIUO or ICEoNNUHSNhoppingSequenceNumber0 (cyclic hopping)1...63 (random hopping)IUO and IFHo00UMOunderlayMaioOffset0..62(IUO or ICE) and IFHo00UMSunderlayMaioStep1..62(IUO or ICE) and FlexMaioMgment and IFHo11UMALunderlayMA0..128(IUO or ICE) and IFH

&A&LDefault parameters / Telemar&C&D&R&P/&N

POC(ZEUO)POC ParametersRangeFeature NameFeatureDefault NokiaDefault macroChangesppl, macro, ppl_RFH, macro_RFHmicro, micro_RFHPENApowerCtrlEnabledY/NbNNNINTpowerControlInterval0..31 (s)b222PMINbsTxPowerMin0..30 (dB) / 2 dB stepb3030-30PMAXbsTxPowerMax0..30 (dB) / 2 dB stepb00xx08INCpowerIncrStepsize2, 4, 6 (dB)b466REDpowerRedStepsize2, 4 (dB)b222PD0pwrDecrLimitBand00..38 (dB) / 2 dB stepb383838PD1pwrDecrLimitBand10..38 (dB) / 2 dB stepb383838PD2pwrDecrLimitBand20..38 (dB) / 2 dB stepb383838PDFpowerDecrQualFactor0, 1b111AENAenableALAY/NbNNNAMINminIntBetweenALA0..30 (s)b101010ALIMpowerLimitALA0..30 (dB) / 2 dBstepb666LDSpcAveragingLevDL / windows size1..32b444LDWpcAveragingLevDL / weighting1..3b122LUSpcAveragingLevUL / windows size1..32b44LUWpcAveragingLevUL / weighting1..3b122QDSpcAveragingQualDL / windows size1..32b11QDWpcAveragingQualDL / weighting1..3b122QUSpcAveragingQualUL / windows size1..32b11QUWpcAveragingQualUL / weighting1..3b122UDRpcUpperThresholdsQualDL / rxqual0..7b0x0UDPpcUpperThresholdsQualDL / px1..32b321616UDNpcUpperThresholdsQualDL / nx1..32b321616UURpcUpperThresholdsQualUL / rxqual0..7b0x0UUPpcUpperThresholdsQualUL / px1..32b321616UUNpcUpperThresholdsQualUL / nx1..32b321616LDRpcLowerThresholdQualDL / rxqual0..7b33x3LDPpcLowerThresholdQualDL / px1..32b333LDNpcLowerThresholdQualDL / nx1..32b444LURpcLowerThresholdsQualUL / rxqual0..7b33x3LUPpcLowerThresholdsQualUL / px1..32b333LUNpcLowerThresholdsQualUL / nx1..32b444LQRpcLowerThresholdsQual144 / rxqual0..7b333LQPpcLowerThresholdsQual144 / px1..32b333LQNpcLowerThresholdsQual144 / nx1..32b444UDRpcUpperThresholdsLevDL / rxlev-110..-47 (dBm)b-70-62x-68UDPpcUpperThresholdsLevDL / px1..32b111UDNpcUpperThresholdsLevDL / nx1..32b111UURpcUpperThresholdsLevUL / rxlev-110..-47 (dBm)b-70-74x-72UUPpcUpperThresholdsLevUL / px1..32b111UUNpcUpperThresholdsLevUL / nx1..32b111LDRpcLowerThresholdsLevDL / rxlev-110..-47 (dBm)b-85-74x-80LDPpcLowerThresholdsLevDL / px1..32b111LDNpcLowerThresholdsLevDL / nx1..32b111LURpcLowerThresholdsLevUL / rxlev-110..-47 (dBm)b-85-86x-84LUPpcLowerThresholdsLevUL / px1..32b111LUNpcLowerThresholdsLevUL / nx1..32b111ALPHAalpha0..10 (0.1 unit)Gb Interface functionalityo888GAMAgamma0..62Gb Interface functionalityo181818IFPtAvgW0..25Gb Interface functionalityo999TFPtAvgT0..25Gb Interface functionalityo131313PRVpb-30..0 / 2 dB stepGb Interface functionalityo-2-2-2


HOC(ZEHO)rapidRangeFeature nameFeatureDefault NokiaDefault macroChangesppl, macro, ppl_RFH, macro_RFH, micro, micro_RFHEICenableIntraHOInterULY/NbYYYEIHenableIntraHOInterDLY/NbYYYEPBenablePwrBudgetHandoverY/NbYYYEMSenableMSDistanceProcessY/NbNNNESDenableSDCCHHandoverY/NbNNNEUMenableUmbrellaHandoverY/NbNNNEFAenaFastAveCallSetupY/NbNNNEFPenaFastAvePcY/NbNNNEFHenaFastAveHoY/NbNNNMIHminIntBetweenHoReq0..31 (s)b555MIUminIntBetweenUnsuccHoAttempt0..31 (s)b333HPUhoPeriodUmbrella0..63b666HPPhoPeriodPBGT0..63b666AWSaveragingWindowsSizeAdjCell1..32b666NOZnumberOfZeroResults0..7b222AACallAdjacentCellsAveragedY/NbNNNLDWShoAveragingLevDL / windows size1..32b676LDWhoAveragingLevDL / weighting1..3b122LUWShoAveragingLevUL / windows size1..32b666LUWhoAveragingLevUL / weighting1..3b122QDWShoAveragingQualDL / windows size1..32b111QDWhoAveragingQualDL / weighting1..3b122QUWShoAveragingQualUL / windows size1..32b111QUWhoAveragingQualUL / weighting1..3b122QDRhoThresholdsQualDL / rxqual0..7b44x4QDPhoThresholdsQualDL / px1..32b444QDNhoThresholdsQualDL / nx1..32b666QURhoThresholdsQualUL / rxqual0..7b44x4QUPhoThresholdsQualUL / px1..32b444QUNhoThresholdsQualUL / nx1..32b666LDRhoThresholdsLevDL / rxlev-110..-47 (dBm)b-95-91xx-93LDPhoThresholdsLevDL / px1..32b111LDNhoThresholdsLevDL / nx1..32b111LURhoThresholdsLevUL / rxlev-110..-47 (dBm)b-95-103xx-97LUPhoThresholdsLevUL / px1..32b111LUNhoThresholdsLevUL / nx1..32b111IDRhoThresholdsInterferenceDL / rxlev-110..-47 (dBm)b-85-79xx-83IDPhoThresholdsInterferenceDL / px1..32b111IDNhoThresholdsInterferenceDL / nx1..32b111IURhoThresholdsInterferenceUL / rxlev-110..-47 (dBm)b-85-91xx-87IUPhoThresholdsInterferenceUL / px1..32b111IUNhoThresholdsInterferenceUL / nx1..32b111MSWSmsDistanceAveragingParam / window size1..32b102020MSRmsDistanceHoThresholdParam / range0..63 (bits)b636363MSPmsDistanceHoThresholdParam / px1..32b11010MSNmsDistanceHoThresholdParam / nx1..32b11616METHsuperReuseEstMethodAVE (average taking method)MAX (maximum taking method)ICE (handover support for Intelligent Coverage Enhancement)NONE (Intelligent Underlay Overlay is not in use for this cell)IUOoNONENONENONEMIUminIntUnsuccIuoHo0..31 (s)IUOo3320MIRminIntIuoHoReqBQ0..255IUOo101010CGRsuperReuseGoodRxLevThreshold-110..-47 (dBm)IUOo-80-80-80CGPsuperReuseGoodRxLevThreshold / px1..32IUOo888CGNsuperReuseGoodRxLevThreshold / nx1..32IUOo101010CBRsuperReuseBadRxLevThreshold-110..-47 (dBm)IUOo-85-85-85CBPsuperReuseBadRxLevThreshold / px1..32IUOo222CBNsuperReuseBadRxLevThreshold / nx1..32IUOo666BCIsuperReuseBadCiThreshold-127..127 (dB)IUOo1010BPXsuperReuseBadCiThreshold / px1..32IUOo22BNXsuperReuseBadCiThreshold / nx1..32IUOo66GCIsuperReuseGoodCiThreshold-127..127 (dB)IUOo1717GPXsuperReuseGoodCiThreshold / px1..32IUOo88GNXsuperReuseGoodCiThreshold / nx1..32IUOo1010AVERallInterfCellsAveragedY/NIUOoNNSIZEintfCellAvgWindowSize1..32IUOo1010ZEROintfCellNbrOfZeroResults0..31IUOo22TIMminBsicDecodeTime0..128 (SAACHs period)IUOo1010EFHOenableInterFrtIuoHoREG / SUP / DISIUOoDISDISETAenaTchAssSuperIUO0..32IUO and Directed Retryo01ATCIamhTrafficControlIUOY/NAMHoNNATCMamhTrafficControlMCNY/NAMHoNNATPMamhTrhoPbgtMargin-24 .. 24 (dBm) or N (not active)AMHoNN-ciEstMethodAVE / MAX / NONEC/I Based Handover Candidate EvaluationoNONENONEL1lowerCILimit-128..127 (dB)C/I Based Handover Candidate Evaluationo3030L2lowerCILimit-128..127 (dB)C/I Based Handover Candidate Evaluationo2525L3lowerCILimit-128..127 (dB)C/I Based Handover Candidate Evaluationo2020L4lowerCILimit-128..127 (dB)C/I Based Handover Candidate Evaluationo1717L5lowerCILimit-128..127 (dB)C/I Based Handover Candidate Evaluationo1313L6lowerCILimit-128..127 (dB)C/I Based Handover Candidate Evaluationo99P1priorityAdjStep-8..7C/I Based Handover Candidate Evaluationo33P2priorityAdjStep-8..7C/I Based Handover Candidate Evaluationo11P3priorityAdjStep-8..7C/I Based Handover Candidate Evaluationo00P4priorityAdjStep-8..7C/I Based Handover Candidate Evaluationo-1-1P5priorityAdjStep-8..7C/I Based Handover Candidate Evaluationo-2-2P6priorityAdjStep-8..7C/I Based Handover Candidate Evaluationo-5-5P7priorityAdjStep-8..7C/I Based Handover Candidate Evaluationo-8-8CNThoThresholdsRapidLevUlN0..32Chained cells in rapid field dropo00xRPDHoThresholdsRapidLevUl-110 ... -47 (dBm)Chained cells in rapid field dropo-110-110xERFDerfdEnabledDIS / UL / DL / UDLEnhanced Rapid Field DropoDISDISERMWddeWindow1..32Enhanced Rapid Field Dropo22ERDerfdOver0..64Enhanced Rapid Field Dropo1010ERAWmodifiedAveWinNcell1..32Enhanced Rapid Field Dropo22ERZmodifiedNOZ1..32Enhanced Rapid Field Dropo11ERTddeThresholdsLev0..63Enhanced Rapid Field Dropo1010ERPddeThresholdsLev / px1..32Enhanced Rapid Field Dropo22ERNddeThresholdsLev / nx1..32Enhanced Rapid Field Dropo33LSLlowerSpeedLimit0..255Fast moving MS handling in macro cello00USLupperSpeedLimit0..255Fast moving MS handling in macro cello00MSAmsSpeedAveraging1..32Fast moving MS handling in macro cello44STNmsSpeedThresholdNx1..32Fast moving MS handling in macro cello66STPmsSpeedThresholdPx1..32Fast moving MS handling in macro cello33SDSmsSpeedDetectionState0..100MS Speed Detection Stateo00MAXmaxMSDistanceHOThreshold0..63Improved solution for Extended cell radiuso6363MINminMSDistanceHOThreshold0..63Improved solution for Extended cell radiuso22


ADJ(ZEAO)Target cellADCE ParametersRangeFeature NameFeatureDefault NokiaSource cellChangesMacroMacroAdjacentCellIdLACLAC0..65535b--xx (auto)CICellId0..65535b--FREQbCCHFrequency512..885b--xxx (auto)bsIdentityCodeNCCNCC0..7b--BCCBCC0..7b--xxx (auto)PMRGhoMarginPBGT(n)-24..+63 (dB)b66xx6LMRGhoMarginLev(n)-24..+24 (dB)b333QMRGhoMarginQual(n)-24..+24 (dB)b0-4-4MRGSenableHoMarginLevQual(n)Y/NbYYYPRIhoPriorityLevel(n)0..7b33x3OFhoLoadFactor(n)0..7b111SLrxLevMinCell(n)-110..-47 (dBm)b-100-100-100AUCLhoLevelUmbrella(n)-110..-47 (dBm)b-47-47xx-47PMAXmsTxPwrMaxCell(n)0..36 (dBm) / 2 dB stepb303033SYNCsyncronised(n)Y/NbNNxxxNTRHOtrhoTargetLevel(n)N, -109..-47 (dBm)bNNNDRTdrThreshold(n)-110..-47 (dBm)Directed Retry or Intelligent Directed Retryo-100-85-85POPTmsPwrOptLevel-110..-47 (dBm) / NOptimization of the MS Power Level in HandoversoNNFMTFastMovingThreshold(n)0..255 (SACCH frames)Fast moving MS handling in macro cello00x0ACLAdjacentCellLayer(n)SAME / LOWER / UPPER / NFast moving MS handling in macro celloNSAMESAMECTYcellTypeGSM / MCNIntelligent Directed RetryoGSMGSMCHAINchainedAdjacentCellY/NChained cells in rapid field dropoNNHOTAhoTargetArea0..3Improved solution for extended range cello00ICinterferedCell0..3Dynamic Hotspoto00DADLdadlbTargetCellY/NDirect Access to Desired Layer/BandoNN


TRXTRX ParametersRangeFeature NameFeatureDefault NokiaDefault MacroChangesTRXTransceiver-Id1..16b--FREQinitialFrequency512..885b--xxxLEVDoptimumRxLevDL-109..-47 (dBm) / NbNNLEVoptimumRxLevUL-109..-47 (dBm) / NbNNPREFpreferredBCCHMarkP/NbNNTSCtsc0..7b=BCC-xxxFLOfloatingModeF/NbNNGTRXGPRSenabledTRXY/NGb Interface functionalityoYYHRShalfRateSupportY/NHalf RateoYYLAC1trxIntfCell / LAC0..65535IUOo--LAC2trxIntfCell / LAC0..65535IUOo--LAC3trxIntfCell / LAC0..65535IUOo--LAC4trxIntfCell / LAC0..65535IUOo--LAC5trxIntfCell / LAC0..65535IUOo--LAC6trxIntfCell / LAC0..65535IUOo--LAC7trxIntfCell / LAC0..65535IUOo--LAC8trxIntfCell / LAC0..65535IUOo--LAC9trxIntfCell / LAC0..65535IUOo--LAC10trxIntfCell / LAC0..65535IUOo--CI1trxIntfCell / CI0..65535IUOo--CI2trxIntfCell / CI0..65535IUOo--CI3trxIntfCell / CI0..65535IUOo--CI4trxIntfCell / CI0..65535IUOo--CI5trxIntfCell / CI0..65535IUOo--CI6trxIntfCell / CI0..65535IUOo--CI7trxIntfCell / CI0..65535IUOo--CI8trxIntfCell / CI0..65535IUOo--CI9trxIntfCell / CI0..65535IUOo--CI10trxIntfCell / CI0..65535IUOo--T1CiEstType0/1IUOo00T2CiEstType0/1IUOo00T3CiEstType0/1IUOo00T4CiEstType0/1IUOo00T5CiEstType0/1IUOo00T6CiEstType0/1IUOo00T7CiEstType0/1IUOo00T8CiEstType0/1IUOo00T9CiEstType0/1IUOo00T10CiEstType0/1IUOo00W1CiEstWeighting0..10IUOo11W2CiEstWeighting0..10IUOo11W3CiEstWeighting0..10IUOo11W4CiEstWeighting0..10IUOo11W5CiEstWeighting0..10IUOo11W6CiEstWeighting0..10IUOo11W7CiEstWeighting0..10IUOo11W8CiEstWeighting0..10IUOo11W9CiEstWeighting0..10IUOo11W10CiEstWeighting0..10IUOo11L1LevelAdjustment-63..63 (dB)IUOo00L2LevelAdjustment-63..63 (dB)IUOo00L3LevelAdjustment-63..63 (dB)IUOo00L4LevelAdjustment-63..63 (dB)IUOo00L5LevelAdjustment-63..63 (dB)IUOo00L6LevelAdjustment-63..63 (dB)IUOo00L7LevelAdjustment-63..63 (dB)IUOo00L8LevelAdjustment-63..63 (dB)IUOo00L9LevelAdjustment-63..63 (dB)IUOo00L10LevelAdjustment-63..63 (dB)IUOo00FRTtrxFrequencyType0..16IUO or ICEo00DALdirectAccessLevel-109..-47 dBm / NIUO or ICEoNNETRXeTrxIndN/EExtended cell radiusoNN

&CTRX Parameters&LDefault Parameters / Telemar&C&D&R&P/&N

TRX configCell with 1 TRXTRX-1MBCCHBTCHFTCHFTCHFTCHFTCHFTCHFTCHFGDEFChannel_type TRX-170000000Cell with 2 TRXsTRX-1MBCCHSDCCBTCHFTCHFTCHFTCHFTCHFTCHFTRX-2TCHFTCHFTCHFTCHFTCHFTCHFTCHFTCHFGDEFChannel_type TRX-148000000Channel_type TRX-200000000Cell with 3 TRXsTRX-1MBCCHSDCCBTCHFTCHFTCHFTCHFTCHFTCHFTRX-2SDCCHTCHFTCHFTCHFTCHFTCHFTCHFTCHFTRX-3TCHFTCHFTCHFTCHFTCHFTCHFTCHFTCHFGDEFChannel_type TRX-148000000Channel_type TRX-230000000Channel_type TRX-300000000Cell with 4 TRXsTRX-1MBCCHSDCCBTCHFTCHFTCHFTCHFTCHFTCHFTRX-2SDCCHTCHFTCHFTCHFTCHFTCHFTCHFTCHFTRX-3TCHFTCHFTCHFTCHFTCHFTCHFTCHFTCHFTRX-4TCHFTCHFTCHFTCHFTCHFTCHFTCHFTCHFGDEFChannel_type TRX-148000000Channel_type TRX-230000000Channel_type TRX-300000000Channel_type TRX-400000000Channel-typeDescription0TCHF (TCH Full rate)1TCHH (TCH Half Rate)2TCHD (TCH Dual rate means full and half)3SDCCH4MBCCH (Non combined BCCH)5MBCCHC (Combined BCCH that means BCCH-SDCCH/4)7MBCCB (Combined BCCH with Cell Broadcast that means BCCH-SDCCH/3-CBCH)8SDCCB (SDCCH Combined with Cell Broadcast which means SDCCH/7-CBCH)9Not Used10E-RACH (Extended RACH used for extended cell feature)

Chart21967024552185323712321557752706788912614509392449941903180838747187695850889617218908894092521700882388239524514769526465585942684

sdcch_radio_failsdcch_rf_old_hoSDCCH Radio Failures

Sheet11-Dec-082-Dec-084-Dec-085-Dec-086-Dec-087-Dec-088-Dec-089-Dec-0810-Dec-0811-Dec-0812-Dec-0813-Dec-0814-Dec-0815-Dec-0816-Dec-08sdcch_seiz_att260422082686739827367340284609192814628027071763275636412681814126486744264679872639770026182123256558202735267326978915sdcch_assign2595173626820364273145462840673928078438266084052749938126780504264355852641030826352009261410232547173027309231269426571-Dec-082-Dec-084-Dec-085-Dec-086-Dec-087-Dec-088-Dec-089-Dec-0810-Dec-0811-Dec-0812-Dec-0813-Dec-0814-Dec-0815-Dec-0816-Dec-08sdcch_radio_fail19670221853223215527067826145024499418083818769588961890889252188238952459526485942sdcch_rf_old_ho455371775891939190374785072194070082314766556841-Dec-082-Dec-084-Dec-085-Dec-086-Dec-087-Dec-088-Dec-089-Dec-0810-Dec-0811-Dec-0812-Dec-0813-Dec-0814-Dec-0815-Dec-0816-Dec-08sdcch_abis_fail_call157798317834091914073218632321309132058120171750117225781470204164498117540781739174188793318132931710038sdcch_abis_fail_old313104878318615451810

Sheet1

sdcch_seiz_attsdcch_assignSDCCH Seiz Vs. Assignment

Sheet2

sdcch_radio_failsdcch_rf_old_hoSDCCH Radio Failures

Sheet3

sdcch_abis_fail_callsdcch_abis_fail_oldSDCCH Abis Failures

Chart190.569398842388.6369507041WED3-Dec87.847166771786.0754807154SAT6-Dec88.496125108593.143689019391.454964156298.44083336298.558304377198.205244934598.492137810398.160615307598.46529106398.6818229299

SDCCH Completion Rate (BBH) >=98%

CITY DETAILSCITY DetailsCITY CODECITY NAMEBTS Hardware UsedAHDAhmedabadNOKIASRTSuratNOKIABRDBarodaNOKIARJTRajkotNOKIABVNBhavnagarNOKIAJAMJamnagarNOKIAGNDGandhidhamNOKIAMRBMorbiNOKIAJUNJunagadNOKIAANDAnandNOKIA

ENTIRE NETWORKGUJARATDaily Performance ReportasDateParameterTargetDatexxx1-Dec2-Dec3-Dec4-Dec5-Dec6-Dec7-Dec8-Dec9-Dec10-Dec11-Dec12-Dec13-Dec14-Dec15-Dec16-Dec18-Dec19-Dec20-Dec21-Dec22-Dec23-Dec24-Dec25-Dec26-Dec27-Dec28-Dec29-Dec30-Dec31-DecxxxDayDayMONTUEWEDTHUFRISATSUNMONTUEWEDTHUFRISATSUNMONTUETHUFRISATSUNMONTUEWEDTHUFRISATSUNMONTUEWED(A)INSTALLED CAPACITYSwitching Network Capacity1HLR ('000 Subscribers)n.a11821118211182111821118211182111821118211182111821118211182111821118211182111821118211182111821118211182111821118211182111821118211ANo. of HLR Elementn.a444444444444444444444444442Number Of (pure) MSCs + (pure) GMSCsn.a10101010101010101010101010101010101010101010101010102ANumber Of (pure) MSCs - out of 2n.a888888888888882288822888882BNumber Of (pure) GMSCs - out of 2n.a222222222222228822288222223Total equipped MSC Capacity (Erlangs)n.a4054804054804054804054804054804054804054804054804054804054804054804054804054804054804054804054804054804054804054804054804054804054804054804054804054804054804Total MSC Capacity (BHCA)n.a23214000232140002321400023214000232140002321400023214000232140002321400023214000232140002321400023214000232140002321400023214000232140002321400023214000232140002321400023214000232140002321400023214000232140004aTotal No. of MSS888888888888888888888888884bTotal equipped MSS Capacity (Subs.)776200077620007762000776200077620007762000776200077620007762000776200077620007762000776200077620007762000776200077620007762000776200077620007762000776200077620007762000776200077620004cTotal No. of MGW22222222222222222222222222222222222222222222222222224dNo. of MGW Locations555555555555555555555555554eTotal equipped MGW Capacity (Subs)440000044000004400000440000044000004400000440000044000004400000440000044000004400000440000044000004400000440000044000004400000440000044000004400000440000044000004400000440000044000004fNo. of BSCs under MGW7171717171717171717171717171717171717171717171717171Radio Network Capacity5Number of BSCn.a1341341341341341341341341341341341341341341341341341341341341341341341341341346Total BSC offered capacity (TRX)n.a88046880468804688046880468804688046880468804688046880468804688046880469035690356903569035690356903569035690356903569035690956909567Total BSC offered capacity (Erlangs)n.a5226795226795226795226795226795226795226795226795226795226795226795226795226795226795364005364005364005364005364005364005364005364005364005364005399645399648Total Sitesn.a551855185522552355235525552555255526552655315531553155365545554555525556556555765592560056065630565656908AMacron.a545854585462546354635465546554655466546654715471547154765485548554925496550555165532554055465570559656308BMicron.a888888888888888888888888888CIBSn.a52525252525252525252525252525252525252525252525252528DOutdoor BTS sitesn.a180818081810181018101811181118111811181118131813181318131814181418151815181618181821182118221823183018368EIndoor BTS sitesn.a365036503652365336533654365436543655365536583658365836633671367136773681368936983711371937243747376637949Total sites sharedn.a379137913791379137913791379137913791379137913791379137913791379137913791379137913791379137913791379137919AVodafone sharing other operator sitesn.a225022502250225022502250225022502250225022502250225022502250225022502250225022502250225022502250225022509BVodafone sites shared by other operatorsn.a154115411541154115411541154115411541154115411541154115411541154115411541154115411541154115411541154115419CTotal Census towns covered2432432432432432432432432432432432432432432432432432432432432432432432432432439DTotal towns covered (including census)3186318631863186318631863186318631863186318631863186318631863186318631863186318631863186318631863186318610Cellsn.a164791647916480165011648316512165151651416514165161651616516165141651616624166241656416573165691664516645166901669016706168261690610ANo of zz cells42842037138439338837535838939035435135736361258962255554448555956456462054039110BNo of zl cells282828252825252525252525252542424242424242424243434310CNo of zq cells54954952548751652952651146040437537536330641341332033233242542544344620329938210DNo of cells EDGE enabled159151591515930159331592615944159451594715947159431594315943159431594316064160391592315935159341608416070160941609616142162431631310ENo of cells GPRS enabled163201631116085158931630016163161591608715942159221592215922159221592216447164331629716364163601651216493165231651216532166321674011TRXsn.a614116141861416616666148061584615936157161766617686176561765617626166861890618586175561776617576190861892619906198962036623236250511ATRXs Faulty232227199121218132724167112444272727274823193831NA11BTotal Voice TSLn.a39674639677639674339851339723339788439794439775039920639921639920039920039918039846939963639939539884439896839884839970139958340017640017040046140218440329511CTotal dedicated GPRS/EDGE TSLn.a423294234442340423924234642416424224241942423424244242142421424214242342794427944264642664426554284242843429364293342978432714344912ARepeaters (indoor)n.a54854854854854854854854854854854854854854854854854854854854854854854854854854812BRepeaters (outdoor)n.a0000000000000000000000000013ASpectrum alloted (GSM 900)n.a7.8 & 6.2 MHz7.8 & 6.2 MHz7.8 & 6.2 MHz7.8 & 6.2 MHz7.8 & 6.2 MHz7.8 & 6.2 MHz7.8 & 6.2 MHz7.8 & 6.2 MHz7.8 & 6.2 MHz7.8 & 6.2 MHz7.8 & 6.2 MHz7.8 & 6.2 MHz7.8 & 6.2 MHz7.8 & 6.2 MHz7.8 & 6.2 MHz7.8 & 6.2 MHz7.8 & 6.2 MHz7.8 & 6.2 MHz7.8 & 6.2 MHz7.8 & 6.2 MHz7.8 & 6.2 MHz7.8 & 6.2 MHz7.8 & 6.2 MHz7.8 & 6.2 MHz7.8 & 6.2 MHz7.8 & 6.2 MHz13BSpectrum alloted (GSM 1800)n.a2 MHz2 MHz2 MHz2 MHz2 MHz2 MHz2 MHz2 MHz2 MHz2 MHz2 MHz2 MHz2 MHz2 MHz2 MHz2 MHz2 MHz2 MHz2 MHz2 MHz2 MHz2 MHz2 MHz2 MHz2 MHz2 MHz14ARadio Network Capacity (Erl) - voice(FR)n.a278153.07278176.37278145.22279559.69278552.71279007.65279046.44278876.10280100.68280102.27280089.34280089.34280078.90279453.234399998280053.71279847.30279604.65279677.10279590.36280030.98279929.39280272.67280267.30280457.76281487.79282147.3414BRadio Network Capacity (Erl) - Capacity gain due to HR28823.7630485.4331264.3932525.3329785.6232714.5532072.7732645.4130016.2629180.4127688.9027761.4231787.1330496.7028545.2724797.7828746.5227705.0326880.2825198.5726094.1025305.3922994.4626038.1826031.1129059.6114CRadio Network Capacity (Erl) - datan.a36680.9536694.9736691.3236756.8636703.0636762.1936767.4736763.6436789.9436790.2036787.3536787.3536787.1836780.951099999837088.0737084.5736969.0436983.5936975.4437123.5137122.9837197.7337194.9337232.8837470.6137613.7114DRadio Network Capacity (Erl) - Voice + Datan.a314834.01314871.34314836.54316316.55315255.77315769.84315813.90315639.74316890.62316892.47316876.69316876.69316866.09316234.185499998317141.78316931.87316573.69316660.69316565.79317154.48317052.38317470.40317462.23317690.64318958.39319761.0514ETotal Capacity - FR + Capcity Gain Due to HR306976.83308661.79309409.61312085.02308338.33311722.19311119.21311521.51310116.93309282.68307778.24307850.76311866.03309949.94308598.98304645.08308351.17307382.13306470.64305229.55306023.49305578.06303261.77306495.94307518.90311206.9614FRadio Network Capacity Due to Locked TRX(Erl) - Voice + Data1040.321702.86979.891585.921206.821357.771190.601094.252073.371400.471342.541342.541346.861356.34392509.871851.062191.821759.371750.171867.431817.771849.822087.002847.482919.162372.76(B)SUBSCRIBERS DATAHLR Subs (at 00:00 hrs)8794245878750987854288783218877014087661488762144875289987530418758147875069787506978750697NA88455398844981884200188431968934488904208890348029078337907838490753589109376916009315ARegistered, with a valid VLR Addressn.a6221245622521562395876244687626735362646066270226627826562910866279387NA6319183632357563323624603486N.ANANANANANANANA64058516414093642275915BRegistered, with an invalid VLR Address (e.g : BLANK)n.a2583457259839825598512568944251820025055712499773248454324702712484579NA2432336242555324224902029642N.A.NANANANANANANA26727112698579274644116Un-Registeredn.aNA17Total HLR96590008791232878909487864288788738NA87691908762678876074887587838769199NANA87487378756724884720388450408845210884539088671979042421NA9080531NA91110369168027916288517APeak Count for HLR1 (HLRU : AUC Subscribers)37000003406396 :35188513405192 :35176463402559 :35150113401950 :3514400NA3390906 :35033493386205 :34986473380608 :34930473380854 :34932913390909 :3503349NANA3375977 :34884103378253 :34906893376698 :34891293375754 :34881853376104 :34885333373174 :34856003377830 :34902533441024 :3553446NA3446413 :3558830NA3454865 :35672823458267 :35706813454541 :356694817BPeak Count for HLR2 (HLRU : AUC Subscribers)23450002217394 :22761032217615 :22763232218562 :22772602222099 :2280796NA2216993 :22756882215342 :22740372216011 :22747062216378 :22750682216996 :2275688NANA2214537 :22732262215499 :22741852214554 :22732392214056 :22727412213402 :22720852212376 :22710592217005 :22756862220917 :2279597NA2226945 :2285621NA2226531 :22852032226354 :22850252224827 :228349617CPeak Count for HLR3 (HLRU : AUC Subscribers)36140003167442 :31674453166287 :316

2g Radio Network Optimization Training ( Practical Workshop)

Documents

Transcript of 2g Radio Network Optimization Training ( Practical Workshop)