ZTE GERAN Counters & KPIsZTE University

ObjectivesAt the end of this course, you will be able to:Master ZTE traffic statistic functionUnderstand the meaning of common-used traffic statistic indicesMaster the methods to analyze and locate the network problems by the way of traffic statistic analysis

ContentsOverview of traffic statisticTraffic statistic KPILocate and analyze network problems Traffic statistic analysis instance

Introduction of ZTE traffic statistic

KPI of CS traffic statisticPrimal indicesSDCCH congestion rateSDCCH assignment success rateSDCCH call drop rateTCH congestion rateTCH assignment success rateTCH call drop rateHandover success rateRandom access success ratePaging success rateIntegrated indicesTraffic call drop rateBad cell rateTCH allocation rateRadio access success rate

KPI of PS traffic statisticTBFUL TBF Establishment Success Rate DL TBF Establishment Success Rate UL Signaling TBF Failure Rate DL Signaling TBF Failure Rate UL GPRS Data TBF Failure Rate DL GPRS Data TBF Failure Rate UL EDGE Data TBF Failure Rate DL EDGE Data TBF Failure Rate

KPI of PS traffic statisticLLCDL LLC Signaling Frame Discard Rate DL LLC GPRS Data Frame Discard Rate DL LLC EDGE Data Frame Discard Rate ThroughputUL GPRS Throughput DL GPRS Throughput UL EDGE Throughput DL EDGE Throughput

CS traffic measurementAssignment Measurement Assignment counter describers the assignment process. As many attempts can be made if no channel is available in the first assignment attempt, it is necessary to make a completed description of the whole assignment process instead of the assignment processes of TCH/F or TCH/H. These counters are used to analyze influences of forced release, queuing and directed retry, to assignment success rate from the viewpoint of calling. 1

CS traffic measurementHandover cause measurement Handover cause counter is used for checking MS handover causes. According to cell radio environment and BSC settings, handover algorithm judgment module can carry out handover due to several different handover causes, so as to realize functions such as optimizing resource usage, improving call quality and rescuing calls.2

CS traffic measurementCall drop measurement Channels that take part in the measurement statistic include SDCCH, TCH/F and TCH/H. Service types include signaling, voice and data. Counted call drop causes include RMM losses contact with SMM, BTS radio link failure, LAPD link failure, OMCR forced release, forced release by other calls, handover failure, as well as other failure. 3

CS traffic measurementRadio resource available measurement Radio resource available measurement counters count the number, mean number and the maximum busy number of available SDCCH, TCH/H and TCH/F, as well as total busy and congestion time of these channels in the cell. 4

CS traffic measurementGeneral handover measurement General handover counter is used to find out MS handover successes, failures, and frequency of abnormal events during handover. After configured with inter-system handover or concentric circle, general handover counter is also used to find out inter-cell traffic sharing to improve the wireless planning.5

CS traffic measurementAdjacent cell handover measurement Adjacent cell handover counter is used to record the number of outgoing handover or incoming handover so as to find out the handover between the cell and its adjacent cell which lays a basis for configuration of adjacent cell and improves service quality of the cell through handover. 6

CS traffic measurementRadio access measurement Radio access counter is mainly used to observe MS radio random access process as the reference of radio access parameter adjustment, signaling channel allocation strategy, etc. Several possible causes of radio access are listed here. Access statistics related to GPRS is not listed here but in the category of other access request temporarily. The number of access request is that of receiving Channel Required message; the number of successful access process is that of sending Immediate Assignment message. 7

CS traffic measurementRadio measurement Radio measurement items mainly include UL/DL quality, signal strength, TA, interference band and RQ value of radio channels. The UL/DL quality, signal strength, TA and RQ value are counted after measurement report or pre-processing measurement report sent by BTS is received; BSC updates interference band status in database after receiving measurement report or pre-processing measurement report. The value of interference band can be inquired in database when periodical measurement is reported. 8

CS traffic measurementSub cell statistics Sub cell statistics counter is used to find out operation status of the sub cell in radio environment. It focuses on inter-sub-cell handover and relevant counting at the second sub cell so as to check traffic absorption condition by the second sub cell. 9

CS traffic measurementMS TA measurement MS TA counters are used to check the value of TA in MS measurement reports. TA can reflect the relative location of MS in the cell. If most of the TAs are in very high level, network planning should be remade, such as, increasing the site density. 10

CS traffic measurementSAPI3 measurement MO-SM is short message of mobile originating call; MT-SM is short messages of mobile terminating call. In conversation status, the MS can receive point-to-point message so the mobile caller maybe the other side of receiving short message at one time. On the wireless side, short message could be transmitted by the following five channels: SACCH/F, SACCH/H, SDCCH, FACCHF and FACCHH. So far the statistics counting has been realized by the channel of SACCH/F, SACCH/H and SDCCH.11

CS traffic measurementTRX measurement TRX measurement is to measure the success or failure condition of channel activation, assignment, and handover in the unit of carrier. It also can measure carrier interference band, maximum and minimum UL & DL level condition, to learn the status of different carriers, providing evidence for adjustment and maintenance.12

CS traffic measurementTimeslot measurement Timeslot counters are used to view the radio transceiver environment of a MS in a particular timeslot, including the link quality and strength in the timeslot. These data is sent to Network side through measurement report. If signal strength in some timeslots is weak, then it can be improved by changing send and receive power. 13

CS traffic measurementSDCCH measurement SDCCH counters describe allocation, occupation, assignment, use of resources related to SDCCH, which as SDCCH configuration and parameters adjustment basis. Allocation of SDCCH is mainly in the process of immediate assignment and handover. Handover includes internal and external handover. The statistic unit in this measurement is cell. 14

CS traffic measurementTCH/F measurement & TCH/H measurement In GSM BSC signaling system, allocation and usage of TCH/F(TCH/H) channel mainly exist in assignment and handover flow, where assignment flow includes immediate assignment and common assignment; handover flow includes internal and external handover. 15

CS traffic measurementAbis interface message counter measurement Abis interface message measurement is mainly for all kinds of messages of Abis interface to count. It is convenient to find out the frequency of all kinds of messages transmitting on Abis interface. When BSC receives the messages sent by BTS, the counter begin to count. 16

CS traffic measurementBTS TRX measurement According to the receiving level and receiving quality in MS measurement report and the receiving level and receiving quality in BTS measurement, BTS decides whether to perform power control for MS or BTS. BTS also performs statistics according to different reasons for power control.There are two ways for power control: common control and rapid control. The power control amplitude in rapid control is larger than that in common control. Besides, BTS periodically samples the power of MS and BTS to get the average power.After the power control measurement task is customized, BTS periodically reports the power control statistic result to BSC through the PC TEST RPT message. The power control measurement result can be used to analyze coverage quality and power control effect and frequency.17

CS traffic measurementBSSMAP message measurement The BSSMAP message measurement performs statistics for various BSSMAP messages at A-interface. It is used to find out the frequency of various BSSMAP messages transmitted at A-interface. When BSC receives the correct BSSMAP message from MSC, the counter counts. 18

CS traffic measurementA-Interface message measurement The A-interface message measurement performs statistics for uplink/downlink DTAP message, BSSMAP message, and received incorrect BSSMAP message. Statistic unit in this measurement is CMP. 19

CS traffic measurementAter message measurement Ater interface message counters are used to collect statistics on messages transceived on Ater interface. It is counted by AterDispatch according to iTC office. 20

PS traffic measurementDownlink data TBF measurement DL TBF process comprises establishment, transmission and release of the DL TBF. The establishment includes the DL TBF establishment on CCCH, PCCCH and PACCH.The release includes normal release and abnormal release of the DL TBF. Abnormal release is used to judge the running of PS service so as to make adjustment.DL transmission measurement mainly focuses on the connecting time of the DL TBF and the number of co-existing DL TBFs. 1

PS traffic measurementUplink data TBF measurement Uplink (UL) data TBF measurement mainly involves processes of establishing TBF, keeping TBF and releasing TBF on cells.2

PS traffic measurementData flow measurement Data flow measurement focuses on the flow related information, including the LLC frames, RLC blocks and TBF connecting time. 3

PS traffic measurementUplink/Downlink RLC statistic measurementRLC blocks are classified into control block and data block based on the content. Data block includes RLC block waiting to be acknowledged (Pending block), retransmitted block (NACK block), and first-transmitted block (new blocks excluding retransmitted RLC block and pending RLC blocks).RLC coding scheme includes CS1 ~ CS4 and MCS1 ~ MCS9. Coding scheme is set at background and can be adjusted by BSC according to the link quality. UL/DL RLC statistics is used to find out the number of RLC blocks with different coding schemes received and sent by BSC as well as coding scheme adjustment times during transmission process. 4

PS traffic measurementPS resource used statistic measurement Statistic counters are used to measure the PS resource usage in each cell, including number of usable PS channels, average and max number of busy PS channels, total busy time of PS channels, total time of PS channel congestion and using of PS channels. 5

PS traffic measurementUplink and Downlink PACCH statistics In transmitting GPRS data service, UL and DL PACCH statistics is used to count the number of receiving and sending controlled messages on PACCH, including packet access reject, packet resource request, packet UL assignment, etc.6

PS traffic measurementDownlink GPRS data TBF statistics DL GPRS data TBF statistics is used to observe the process of GPRS DL TBF establishment, maintenance and release.7Downlink EGPRS data TBF statistics DL EGPRS data TBF statistics is used to observe the process of EGPRS DL TBF establishment, maintenance and release.8

PS traffic measurementUplink GPRS data TBF statistics UL GPRS data TBF statistics collects the information about the establishment, maintain and release of UL GPRS TBF. 9Uplink EGPRS data TBF statistics UL EGPRS data TBF statistics collects the information about the establishment, maintain and release of UL EGPRS TBF.10

PS traffic measurementBSSGP flow statistic BSSGP flow statistics mainly measures the message transmission condition at Gb BSSGP level in GPRS service, to count different signaling messages. This includes the number of packet paging, circuit paging, BVC block, BVC unblock, BVC reset, location request, and location result response, etc.11

PS traffic measurementGb message statistics (BVC cell) Gb message statistics mainly measures transmission number of different PTP messages at Gb BSSGP level in GPRS service (such as RA-CAPABILITY, RADIO-STATUS, DOWNLOAD-BSS-PFC). 12

PS traffic measurementNSVC statistic measurement The NSVC statistic measurement is used to measure signaling interaction and data transmission at NS layer of Gb interface for GPRS service. It counts the number of various messages, such as blocking, unblocking, resetting, and ALIVE. 13

PS traffic measurementNSE statistic measurement The NSE statistic measurement takes a single NSE as the measurement entity. It performs statistics for paging message, status indication message, and signaling BVC resetting message received by NSE at BSS.14

PS traffic measurementNSVC on IPGB HOST measurement The NSVC statistic measurement on IPGB HOST is used to measure signaling interaction and data transmission at NS layer of Gb interface in GPRS service. It also performs statistics for abnormalities in various flows. 15

PS traffic measurementGB Message on IPGB HOST measurement The Gb interface message measurement on IPGB HOST measures the number of transceiving various PTP messages at BSSGP layer of Gb interface in GPRS service, such as RA-CAPABILITY, RADIO-STATUS, and DOWNLOAD-BSS-PFC.16

PS traffic measurementNSE on IPGB HOST measurement The NSE measurement on IPGB HOST takes a single NSE as the measurement entity. It performs statistics for paging message, status indication message, and signaling BVC resetting message received by NSE at BSS.17

ContentsOverview of traffic statisticTraffic statistic KPILocate and analyze network problems Traffic statistic analysis instance

SDCCH measurement pointT3101 Time out

MS

BTS

BSC

CHL_REQ

CHL_RQD

A1

A2

CHL_ACT

CHL_ACT_ACK

A3

IMM_ASS_CMD

IMM_ASS

SABM

EST_IND

A4

SDCCH Counters

SDCCH Counters

SDCCH Counters

Commonly used KPISDCCH Congestion rateSDCCH congestion rate(%) =SDCCH overflows/SDCCH call attempts 100= (C900060005+C900060011+C900060039) /(C900060003+C900060010+C900060038 ) 100SDCCH assignment success rateSDCCH assignment success rate (%) SDCCH assignment success/ SDCCH assignment attempts100=C900060242/C900060241 100

Commonly used KPISDCCH call drop rateSDCCH call drop rate (%) = SDCCH call drop number/ SDCCH assignment success number 100=C900060053/ (C900060003+C900060010+C900060038 ) 100

TCH congestion statistic point

BTS

BSC

CHL_ACT_ACK

B1

CHL_ACT

ASS_CMD

B2

MSC

BTS

BSC

C1

CHL_ACT

HO_REQ

C2

MSC

CHL_ACT_ACK

TCH Counters

TCH Counters

TCH Assignment statistic point

TCH Counters

Commonly used KPITCH congestion rateTCH congestion rate (exclude handover) = TCH overflows (exclude handover) / TCH attempts (exclude handover) 100 = (C900060020+C900060031+C900060043+C900060047)/(C900060019+C900060030+C900060042+C900060046) 100TCH congestion rate (include handover) = TCH overflows (include handover) / TCH attempts (include handover) 100= (C900060020+C900060031+C900060043+C900060047+ C900060022+C900060033+C900060045+C900060049)/(C900060019+C900060030+C900060042+C900060046+ C900060021+C900060032+C900060044+C900060048) 100

Commonly used KPITCH assignment success rateTCH assignment success rate =TCH assignment success numberexclude handover/ TCH assignment attempts numberexclude handover100=(C900060017+C900060028+C900060036+C900060235+C900060199+C900060210)/(C900060017+C900060028+C900060036+C900060235+C900060199+C900060210+C900060018+C900060029+C900060037+C900060135+C900060200+C900060211)100

Commonly used KPITCH call drop rateTCH call drop rateinclude handover= TCH call drop number / Total number TCH assignment successinclude handover100Trigger pointMonitor CLEAR REQUEST after receiving ASSIGMENT COMPLETE message

Commonly used KPIHandover success rate (Incoming handover)Handover success rate%= Number of handover success / number of handover request 100 = (C900060098+C900060102+C900060120+C900060094+C900060096) /(C900060097+C900060099+C900060100+C900060101+C900060216+C900060119+C900060093+C900060095) 100

Commonly used KPITrafficThe total traffic of all TCH, including TCH/F and TCH/H.Total TCH traffic = Total busy time of TCH/ statistic duration = (C900060129+C900060127)/3600Traffic call drop raitoTotal TCH traffic 60/ total call drop numbers Unit: minuterepresent the average time separation of every two call drops

Commonly used KPIBad cell ratioNumber of bad cells / total number of cells 100%Condition:Busy hours traffic per TCH>0.1Erland TCH call drop rate>3 or TCH congestion rate>5Confirm cell numbers according to average per TCH traffic >0.1Erl

TCH call drop statistic pointRadio link timeout call drop

MS

BTS

BSC

Measurement report(SACCH)

Measurement report(SACCH)

Start T3109

Stop T3109

Clear Command

RF Channel Release

Connection Failure Indication

Clear Complete

F1

MSC

RF Channel Release ACK

Clear request

Radio link timeout

Measurement report(SACCH)

TCH call drop statistic pointIntra cell handover call drop

MSC

BSC

BTS:TRX

MS

ASSIGNMENT COMMAND

CHANNEL ACTIVATE

G1

CHANNEL ACTIVATE ACK

SET T3107

T3107 Timeout

Clear Request

TCH call drop statistic pointIntra BSC handover call drop

BSC

Old BTS:

MS

CHANNEL ACT

MSC

H1

CHANNEL ACT ACK

New BTS

SET T3103

T3103 Timeout

HO_Command

HO_Command

Clear request

TCH call drop statistic pointInter BSC handover call drop

MS

New BTS

New BSC

SET T8

Old BSC

Old BTS

CHL_ACT

HANDOVER REQUIRED

T8 Timeout

HANDOVER COMMAND

I1

Clear request

MSC

CHL_ACT_ACK

HO_REQ_ACK

HANDOVER COMMAND

HANDOVER COMMAND

TCH Call drop counters

Handover signaling statistic pointIntra cell handover

MS

BTS

BSC

CHL_ACT

J1

ASS_CMD

ASS_CMD

SABM

EST_IND

J2

MSC

MEAS_RES

CHL_ACT_ACK

UA

ASS_COM

ASS_COM

HO_PREFORM

MEAS_REP

Handover signaling statistic pointIntra BSC handover

BSC:Ori_Cell

BTS:Ori_Cell

MS

HANDOVER COMMAND

CHANNEL ACT

CHANNEL ACT ACK

HANDOVER COMPLETE

BTS:Des_Cell

HANDOVER COMMAND

HANDOVER COMPLETE

Measurement Report

Handover Algorithm

BSC:Des_Cell

Measurement Report

HANDOVER COMPLETE

K1

K2

Handover signaling statistic pointInter BSC handover

MS

New BTS

New BSC

HO_COM

Old BSC

Old BTS

CHL_ACT

HANDOVER REQUIRED

L1

HANDOVER COMMAND

SABM

MSC

CHL_ACT_ACK

UA

HO_COM

HO_REQ_ACK

HO_DETECT

HO_ACCESS

PHY_INFO

HANDOVER COMMAND

HANDOVER COMMAND

HO_COM

Clear Command

L2

HO_REQ

Handover counters

UL TBF Establishment Success Rate UL TBF Establishment Success Rate This statistic provides UL GPRS signaling TBF, UL EDGE signaling TBF, UL GPRS data TBF, UL EDGE data TBF establishment success rate, which is the important performance index on data service availability to check the condition of data access success in different cells. UL TBF Establishment Success Rate=(C900040025+C900040033+C900040026+C900040034)/(C900040159+C900040160+C900040161+C900040168+C900040163+C900040164+C900040165+C900040166)*100

DL TBF Establishment Success Rate DL TBF Establishment Success Rate This statistic provides DL GPRS signaling TBF, DL EDGE signaling TBF, DL GPRS data TBF, DL EDGE data TBF establishment success rate, which is the important performance index on data service availability to check the condition of data access success in different cells.DL TBF Establishment Success Rate=(C900040007+C900040015+C900040008+C900040016)/(C900040141+C900040142+C900040143+C900040144+C900040145+C900040146+C900040147+C900040148)*100

UL Signaling TBF Failure Rate UL Signaling TBF Failure Rate This statistic provides TBF proportion exceptionally released after UL signaling TBF establishment success. By this performance index, it can determine interference, packet loss, wrong parameter setting, instable link failure may occur in network. UL Signaling TBF Failure Rate=(C900040037+ C900040038+ C900040039+ C900040040+ C900040041+ C900040042+ C900040043+ C900040044+ C900040045+ C900040046)/(C900040025+ C900040033)*100

DL Signaling TBF Failure Rate DL Signaling TBF Failure Rate This statistic provides TBF proportion exceptionally released after DL signaling TBF establishment success. By this performance index, it can determine interference, packet loss, wrong parameter setting, instable link failure may occur in network. DL Signaling TBF Failure Rate =(C900040149+ C900040150+ C900040151+ C900040152+ C900040153+ C900040154+ C900040155+ C900040156+ C900040157+ C900040158)/(C900040007+ C900040015)*100

DL GPRS Data TBF Failure Rate DL GPRS Data TBF Failure Rate This statistic provides TBF proportion exceptionally released after DL GPRS data TBF establishment success. By this performance index, it can determine interference, packet loss, wrong parameter setting, instable link failure may occur in network. DL GPRS Data TBF Failure Rate =(C900040002+C900040003+C900040004+C900040005+C900040006-C900040149-C900040150-C900040151-C900040152-C900040153)/C900040008*100

UL GPRS Data TBF Failure Rate UL GPRS Data TBF Failure Rate This statistic provides TBF proportion exceptionally released after UL GPRS data TBF establishment success. By this performance index, it can determine interference, packet loss, wrong parameter setting, instable link failure may occur in network. UL GPRS Data TBF Failure Rate =(C900040020+C900040021+C900040022+C900040023+C900040024-C900040037-C900040038-C900040039-C900040040-C900040041)/C900040026*100

UL EDGE Data TBF Failure Rate UL EDGE Data TBF Failure Rate This statistic provides TBF proportion exceptionally released after UL EDGE data TBF establishment success. By this performance index, it can determine interference, packet loss, wrong parameter setting, instable link failure may occur in network. UL EDGE Data TBF Failure Rate =(C900040028+C900040029+C900040030+C900040031+C900040032-C900040042-C900040043-C900040044-C900040045-C900040046)/C900040034*100

DL EDGE Data TBF Failure Rate DL EDGE Data TBF Failure Rate This statistic provides TBF proportion exceptionally released after UL EDGE data TBF establishment success. By this performance index, it can determine interference, packet loss, wrong parameter setting, instable link failure may occur in network. DL EDGE Data TBF Failure Rate =(C900040010+C900040011+C900040012+C900040013+C900040014-C900040154-C900040155-C900040156-C900040157-C900040158)/C900040016*100

UL GPRS Throughput UL GPRS Throughput The user UL GPRS data transmitted on air interface divided by the time taken for data transmissionUL GPRS Throughput =C900040058/C900040059*8

DL GPRS Throughput DL GPRS Throughput The user DL GPRS data transmitted on air interface divided by the time taken for data transmission.DL GPRS Throughput =C900040060/C900040061*8

UL EDGE Throughput UL EDGE Throughput The user UL EDGE data transmitted on air interface divided by the time taken for data transmission.UL EDGE Throughput =C900040066/C900040067*8

DL EDGE Throughput DL EDGE Throughput The user DL EDGE data transmitted on air interface divided by the time taken for data transmission.DL EDGE Throughput =C900040068/C900040069*8

DL LLC Signaling Frame Discard Rate DL LLC Signaling Frame Discard Rate The statistic provides the percentage of the discarded downlink LLC signaling frame. DL LLC signaling frame discard rate equals to the number of DL signaling LLC frame discard due to full buffer, exhausted lifecycle, and other exceptions divided by the number of DL signaling LLC frame transmitted .DL LLC Signaling Frame Discard Rate =(C900040052+C900040053+C900040054)/C900040051*100

DL LLC GPRS Data Frame Discard Rate DL LLC GPRS Data Frame Discard Rate The statistic provides the percentage of the discarded DL LLC GPRS data frame.DL GPRS data frame discard rate equals to the number of DL GPRS LLC frame discard due to full buffer, exhausted lifecycle, and other exceptions divided by the number of DL GPRS LLC frame transmitted.DL LLC GPRS Data Frame Discard Rate=(C900040075+C900040076+C900040077)/C900040074*100

DL LLC EDGE Data Frame Discard Rate DL LLC EDGE Data Frame Discard Rate The statistic provides the percentage of the discarded DL LLC edge data frame.DL EDGE data frame discard rate equals to the number of DL EDGE LLC frame discard due to full buffer, exhausted lifecycle, and other exceptions divided by the number of DL EDGE LLC frame transmitted.DL LLC EDGE Data Frame Discard Rate =(C900040048+C900040049+C900040050)/C900040047*100

ContentsOverview of traffic statisticTraffic statistic KPILocate and analyze network problems Traffic statistic analysis instance

Traffic statistic analysis contentsCall dropSDCCH assignmentTCH congestionSDCCH congestionHandoverTCH assignment

General idea

General ideaCombined with:Driving Test: Analyze coveragequalityhandoversignalingCQT: make a great deal of calls in different placeSignaling trace: Collecting signaling through signaling tools or OMCR signaling trace function

Index Analysis Filter MethodHardware InterferenceCoverage Common factorsHandoverRadio parametersIndividual factorFirst common, then individual factor

Common factorsHardwareInterferenceCoverageTCH Call dropHandoverCongestionSDCCH AssignmentTCH Assignment

Hardware problemsTraffic statisticLocate and SolutionCheck transmission errorrepeter self-excitation, TTA noiseTarget cell Channel activation NACK or TIMEOUTCall drop because of terrestrial trunk circuit failureCalibrate clockLocate hardware problems according left traffic statistic, confirm TRX,CMM,TIC,CDU faultsCS basic measurement Abnormal SDCCH and TCH availability, 10%BTS measurementlocate cal drop and assignment failure on TRX levelAlarm managementlocate hardware failureDynamic managementAbnormal TRX occupationCheck clock systemMonitor transmission system

InterferenceTraffic statisticLocate and SolutionFrequency checkanalyze C/I and C/AFrequency scanFind external interferenceDTCheck interference area and quality distributionAdjust BTSs transmit power ,antenna downtilt or frequency etc. to avoid interference;Open FHDTXDPCFix equipment problems (TRXAntenna)CS basic measurementAnalyze interference band level, change with time and traffic BTS measurementlocate interference on TRX level Handover reason measurementratio of up/down link RQ Handover Cell radio measurementAnalyze the distribution of cell level and quality Abis signaling traceAnalyze cells and TRXs with high interference band

CoverageTraffic statisticLocate and solutionMake DT in estimate weak coverage areaAdjust network parameters based on DT Check BTS transmitting power, antenna downtilt and height, Rxlev_ACCESS_MIN, the neighbor cell relationship, RXLEV_MIN of handover candidate cell. Adjust coverage, avoid over-coverageweak coverage and lonely island Increase BTS sites CELL performance high Up/link RQ bad KPI Power control : Low average up/down link signal Rx-LEV Cell radioToo much low signal Rx-LEV Handover reasontoo much rescue handover (Rx-Lev and Rx-QUAL handover)

Call dropTypeRadio link time outHandover failureLAPD call drop

Call drop analysisBSC level reportCELL level reportBTS basic measurementCell radioCELL level reportCS basic AlarmCommon factorParticular factorAlarm analysisTraffic statisticSignaling analysisOther methodFrom whole to particularLocate to TRXEasy to locate and analysis First common, then particularExecute and solution12345solutionConfirm call drop cellCall drop reasonCall drop typeTRX call drop

Reasons of call dropUnreasonable HO parametersCoverageHardware failureInterferenceUnbalance up/down linkOther parametersCall dropCommon factor already discussed

Unreasonable HO parametersTraffic statisticLocate and solutionMake reasonable neighbor cellsAdjust handover parametersCheck if there are unreasonable HO parametersHandover routine measurement: check outgoing handover failureHandover reason measurement: check handover reason and percents of each kind of handover;Adjacent cell handover measurement: Low successful outgoing HO (for some cells)CS basicHO TCH / calling TCH >3

UL/DL unbalanceTraffic statisticLocate and solutionCheck TACDURDUBTS boards and RF cable connectionCheck antenna direction, tiltdown, feeder and jumper connection, antenna connectorCheck VSWRCS basic: UP/DOWN average Rx_LEV.Abis signaling trace: Analyze UP/DOWN average Rx_LEVCell radio measurement: Analyze UP/DOWN average Rx_LEV

Other unreasonable parametersTraffic statisticSolutionModify the unreasonable parametersCheck radio parametersRLT and Rx-Acc-Min

Handover analysisLow HO success rateCS BasicAlarmHO measurementHO reasonHO routineAdjacent cellIncomingOutgoingPBGT RXLEVRXQUALIncoming/Outgoingreason

General analysis ideaHO problem cells: all cells or individual cell?HO direction: outgoing or incoming HO failureHO target cell: service cell With multi-cell or With individual cell.

Checking step of HO Cells of low HO success rateCells of more HO failure numbersAnalyze outgoing/incoming HO failure number, find out main factors of HO failureRegister out/in handover performanceObserve the feature of HO failure: for all neighbor cells or single cell, for all conditions or single reason that lead to HO failure

Probable reasons for HO failureUP/DOWN unbalanceHardwareUnreasonable parametersCoverageInterferenceLow HO success rateCommon factor already discussed

Unreasonable HO parameterTraffic StatisticLocate and solutionCheck Pbgtrescue HO threshold, HO function switch settingCheck TCH assignment due to HO vs calling If handover/call3probably Ping-pong HO exist , check and adjust handover parameters setting Minimum HO intervalPBGT margin etc

Cell performancelow HO success rateBTS measurementfind out TRX with more HO failureHandover reason measurement: check handover reason and percents of each kind of handoverAdjacent HO measurement: find out which two cells have HO failures

Integrated analysisTraffic statisticLocate and solutionTarget cell expansion or traffic balanceHardware troubleshootingAdjust HO parametersAdjacent cell optimizationCell performancetarget cell congestionCS basiclow incoming HO success rate, maybe hardware or interference problemsLow outgoing HO success ratemaybe target cell congestion or unreasonable HO parametersAdjacent cell unreasonable neighbor External cell: frequency, BSIC

TCH congestionCapacity or unbalance trafficData configurationInterferenceCoverageAntenna systemUnreasonable parametersTCH congestionCommon factor already discussed

Shortage of capacity or traffic unbalanceTraffic statisticLocate and solutionExpansion or balance busy and idle cell TRX configurationAdjust coverageoutput power, antenna direction, tiltdown, heightAdjust cell parametersCRORX-ACC-MIN, open traffic HO functionAdjust cell selection priority, cell HO parametersCell performance: Traffic per channel>0.6CS basic: Too much TCH overflowsCell performance: Unbalance trafficHigh congestion rate

Antenna system problemsTraffic statisticSolutionCheck antenna azimuth, downtilt, connection of antenna and feeder system.Cell frequency scan: check the main and diversity antenna measurementCell radio measurement: signal level, quality , interference bandSignaling tracing: measurement report analysis.

Unreasonable cell parametersTraffic statisticSolutionAdjust unreasonable parameterHardware troubleshootingPerformance report: check TCH congestionAlarm statistic: BTS or TRX hardware failureBTS measurement: check if TRX problem?Check cell parameters: Rx-Acc-Min, cell resection parameters

SDCCH congestionSDCCHUnreasonable Para.Capacity limitSDCCH congestionInterferenceUnreasonable LACCommon factor already discussed

Unreasonable parametersTraffic statisticSolutionAdjust parameter: Random access threshold, RACH access thresholdMaxRetransTx-IntegerT3212Dual band parameter adjustmentCS basic: Check reason of SDCCH congestionRadio access: Immediate assignment success / Immediate assignment > 85%Check para: All parameters with relation to radio accessSDCCH available rate

System capacity limitTraffic statisticSolutionExpansionIncrease SDCCH Adjust T3122T3212RACH

Cell performanceBoth TCH and SDCCH congestionCell performanceTCH no congestion but SDCCH congestionCell locationTraffic hub such as airport, railway stationSMS increase greatly

Unreasonable LAC planningTraffic statisticSolutionModify CRHAdjust cell reselection para.Modify T3212Adjust other para.Cell performanceSDCCH congestionCS Basictoo much location updateLAC planningLAC border cross heavy traffic area

InterferenceTraffic statisticSolutionCheck and adjust frequency planningCheck and remove interferenceAdjust access para.Low RACH threshold, at the same time, there is interferenceCell performanceSDCCH congestionCS basicSDCCH invalid access

SDCCH assignment failureCCCH congestionSoftware versionInterferenceBad coverageTransmissionHardwareReasonCommon factor already discussed

SDCCH assignment failureTraffic statisticSolutionAdjust PCH and AGCH block numbersFrequency checkWork out transmission problemsUpgrade software versionCCCH congestionnot enough AGCH CS basicUplink interference band, abnormal UP/DOWN RQAlarmequipment hardware failureTransmission system monitorlocate transmission problemSoftware version

TCH assignment failure

Success assignmentAssignment failure

TCH assignment analysis

OccupationAfter receives CHANNEL REQUIRE command, BSC will inquire channel resources in MP database.Allocation BSC sends Channel Activation to BTS receives BTSs feedback message Channel Activation ACK, then allocation has been done.AssignmentIt is carried out between BSC and MS. When BSC receives Establish Indication, TCH assignment is successful.123

Reason of TCH assignment failureHardware: TRXCDURF cable connectionInterference: C/I,C/A or external interference Antenna feeder: Antenna and feeder damage, linear antenna direction, downtilt not same, VSWR, feeder cable cross connection Unreasonable para: HSN/MAIO, T3107 small, configuration para is different from planning Coverage: weak coverage or UP/DOWN unbalance Repeater: Induce UP/DOWN interference and unbalance

TCH assignment failureTraffic statisticSolutionCheck cell radio paraCheck BERinterference band, decrease interferenceCheck hardware problem Driving test analysisCheck if BSC and BTS software version matchCell performancecells of TCH assignment failureCS Basicinterference bandcall drophandoverUP/DOWN RQ levelAlarmHardwareBTS measurementlocate TRX with TCH assignment failureNMS TRXThe time and number of TCH and SDCCH assignment

ContentsOverview of traffic statisticTraffic statistic KPILocate and analyze network problems Traffic statistic analysis instance

Call drop instanceDescription From 16 March, Cell I102 of BSC80 call drop number increase greatlyCall drop rateinclude handover>7%AnalysisCell performance: call drop type: radio link failureInterference band: a lot of strip 3Check frequency planning: no problemBTS measurement: TRX2 and TRX3 high assignment failure rateAlarm: noHandover parameters: TRX2 and TRX3 have same MAIO

Call drop instanceSolutionChange MAIO of TRX3 to 10

Handover instance 1Description Cell performance: Site A cell 1 handover success rate lowAnalysisUnreasonable parameter: NoFrom OMCR dynamic management: one TRX can not be occupied, probably hardware problemSolutionChange TRX, everything OK

Handover instanceResult

Site name(LAC-CI)HO requestHO successHO success rate(%)D1ALAC8415-CI250233455215.1D1ALAC8415-CI250232216429D1ALAC8415-CI250232662810.5D1ALAC8415-CI2502316015295D1ALAC8415-CI2502316015496.3

TCH congestion instance 1Description From 21 Dec. according to cell performance reportsite 106 sector 3 of BSC8 in Libyan network, there is great TCH congestion, TCH congestion rate (exclude handover)>30%AnalysisThere is no congestion for this sector before, TCH congestion rate increase suddenlyCheck cell performance and alarm of its neighboring cellswe found one neighboring site 127 which locate oppositely suffered power break, a lot of traffic was absorbed by site 106SolutionAfter the power come back ,site 127 work properly, and site 106 TCH congestion disappeared

TCH congestion instance 1

TCH congestion instance 2Description In the evening of 2, April, we configured dynamic GPRS channel to BSC1. and observed at daytime on 3, April, we found TCH congestion rate went up remarkably.AnalysisDecrease dynamic GPRS to one channel per cell before busy hour on 3, April We observed next day and found that, 11654(TCH assignment failure number) of many cells under BSC1 is still very highSignaling trace: Channel Activation failed for all the TCH come from GPRS dynamic channelSolutionChange dynamic GPRS channel to static channel, then to TCH channel, network restored to normal.

SDCCH congestion instanceDescription Site 61, Cell 3 , SDCCH congestion rate increase suddenly after put into service>35%AnalysisCS basic: there are many location update.LAC planning is OKProbably data configuration problemSolutionWe found LAC of Cell 3 is 8198but the LAC of the other two cells is 8199Change back LAC to 8199

SDCCH assignment instanceDescriptionOne BTS connect BSC by satellite , some type of handset can not call properlyAnalysisSignaling trace: there is no EST IND after BSC send IMMDIEATE ASSIGNMENT COMand BSC release the channelFor satellite transmission, the transmission delay between MS and BTS is about 150ms , this led some type of handset can not receive Immediate assignment command within required period. SolutionBSC adopted optimized Immediate assignment process

TCH assignment instanceDescriptionCell 3 of site 1, TCH assignment failure rate:12.28, Call drop rate:6.9%, Handover in success rate:68.38%, Handover out success rate:91.31%AnalysisTCH assignment failure rate>10%, from which we can exclude interference, maybe there is hardware problem.BTS measurement: We found the second TRX has high TCH assignment failure>30%CQT: we found when the second TRX was occupied, the Rx-Lev is 20dB less than that of BCCH.SolutionChange TRX

TCH assignment instance

C900060003:Number of SDCCH seizure attempts for assignment. SDCCH channel allocation attempt is activated by the MS channel request message CHL_REQ. After BSC receives this message, it attempts to allocate channel for the request. If allocation and occupation succeed, C900060003 and C900060004 accumulate simultaneously.If occupation fails and the failure is due to transceiver fault, C900060003, C900060004, and C900060005 do not change.For failures in other cases, C900060003 and C900060005 accumulate simultaneously.C900060005:Number of SDCCH seizure failure for assignment. SDCCH channel allocation attempt is activated by the MS channel request message CHL_REQ. After BSC receives this message, it attempts to allocate channel for the request. If allocation succeeds but occupation fails, this counter accumulates.If the request returns that the transceiver is faulty, this counter does not change.For failures in other cases, this counter accumulates.C900060010:Number of signaling TCH/F seizure attempts for assignment. This counter counts the number of TCH/F channel occupation attempts during assigning signaling channels, including the number of occupation success (C901260002) and the number of occupation failure (C900060011).C900060011:Number of signaling TCH/F seizure failure for assignment. This counter counts the number of TCH/F channel occupation failures during assigning signaling channels. After BSC receives the channel request, it attempts to allocate channel for the request. If occupation fails, this counter accumulates.If the request returns that the transceiver is faulty, this counter does not change.For failures in other cases, this counter accumulates.C900060038:Number of signaling TCH/H seizure attempts for assignment. This counter counts the number of TCH/H channel being attempted to be occupied during signaling channel assignment, including the number of occupation success (C901270002) and the number of occupation failure (C900060039).After BSC receives the channel request massage, it attempts to allocate channel for the request. If allocation and occupation succeed, C900060038 and C901270002 accumulate simultaneously.If the request returns that the transceiver is faulty, C900060038, C901270002, and C900060039 do not change.For other cases, C900060038 and C900060039 accumulate simultaneously. C900060039:Number of signaling TCH/H seizure failure for assignment. This counter counts the number of TCH/H channel occupation failure during signaling channel assignment.After BSC receives the channel request message, it attempts to allocate channel for the request. If occupation fails, this counter accumulates.If the request returns that the transceiver is faulty, this counter does not change.For failures in other cases, this counter accumulates. C900060241:Number of SDCCH assignment attempts. After BSC responds to the channel request to allocate and activate SDCCH channel successfully, BSC sends the IMM_ASS message to notify MS to use this channel. After MS receives this message, it sends SABM frame to BTS on SDCCH. BTS then sends the EST_IND message to BSC after receiving SABM frame.If BSC receives the correct EST_IND message within specified time, it indicates that the SDCCH channel assignment succeeds, C900060241 and C900060242 accumulate simultaneously.If BSC receives the incorrect EST_IND message or T3101 is timeout, it indicates that the SDCCH channel assignment fails, C900060241 and C900060243 accumulate simultaneously.C900060242 :Number of SDCCH assignments success. After BSC responds to the channel request to allocate and activate SDCCH channel successfully, BSC sends the IMM_ASS message to notify MS to use this channel. After MS receives this message, it sends SABM frame to BTS on SDCCH. BTS then sends the EST_IND message to BSC after receiving SABM frame.If BSC receives the correct EST_IND message within specified time, it indicates that the SDCCH channel assignment succeeds, then this counter increments.

C900060053:This counter counts the number of call drops on SDCCH channel due to radio link failure, LAPD link break, or handover failure. Call drop occurs after MS requests for TCH/H channel successfully. The counter increments if call drop is due to the above causes.C900060124:SDCCH busy time. This counter counts the busy time of SDCCHs, which reflects the traffic volume of SDCCH. The counter counts at the following three time points:When an SDCCH is acquired successfully, this counter calculates time and accumulates.When an SDCCH is released, this counter calculates time and accumulates.When the system reports the periodical measurement data, this counter calculates time and accumulates.

C900060003:Number of SDCCH seizure attempts for assignment. SDCCH channel allocation attempt is activated by the MS channel request message CHL_REQ. After BSC receives this message, it attempts to allocate channel for the request. If allocation and occupation succeed, C900060003 and C900060004 accumulate simultaneously.If occupation fails and the failure is due to transceiver fault, C900060003, C900060004, and C900060005 do not change.For failures in other cases, C900060003 and C900060005 accumulate simultaneously.C900060005:Number of SDCCH seizure failure for assignment. SDCCH channel allocation attempt is activated by the MS channel request message CHL_REQ. After BSC receives this message, it attempts to allocate channel for the request. If allocation succeeds but occupation fails, this counter accumulates.If the request returns that the transceiver is faulty, this counter does not change.For failures in other cases, this counter accumulates.C900060010:Number of signaling TCH/F seizure attempts for assignment. This counter counts the number of TCH/F channel occupation attempts during assigning signaling channels, including the number of occupation success (C901260002) and the number of occupation failure (C900060011).C900060011:Number of signaling TCH/F seizure failure for assignment.This counter counts the number of TCH/F channel occupation failures during assigning signaling channels. After BSC receives the channel request, it attempts to allocate channel for the request. If occupation fails, this counter accumulates.If the request returns that the transceiver is faulty, this counter does not change.For failures in other cases, this counter accumulates.C900060038:Number of signaling TCH/H seizure attempts for assignment. This counter counts the number of TCH/H channel being attempted to be occupied during signaling channel assignment, including the number of occupation success (C901270002) and the number of occupation failure (C900060039).After BSC receives the channel request massage, it attempts to allocate channel for the request. If allocation and occupation succeed, C900060038 and C901270002 accumulate simultaneously.If the request returns that the transceiver is faulty, C900060038, C901270002, and C900060039 do not change.For other cases, C900060038 and C900060039 accumulate simultaneously. C900060039:Number of signaling TCH/H seizure failure for assignment . This counter counts the number of TCH/H channel occupation failure during signaling channel assignment.After BSC receives the channel request message, it attempts to allocate channel for the request. If occupation fails, this counter accumulates.If the request returns that the transceiver is faulty, this counter does not change.For failures in other cases, this counter accumulates. C900060053:This counter counts the number of call drops on SDCCH channel due to radio link failure, LAPD link break, or handover failure. Call drop occurs after MS requests for TCH/H channel successfully. The counter increments if call drop is due to the above causes.C900060019:Number of voice TCH/F seizure attempts. This counter counts the number of TCH/F channel being attempted to be occupied during voice channel assignment, including the number of occupation success (C901260021) and the number of occupation failure (C900060020).After BSC receives the channel request massage, it attempts to allocate channel for the request. C900060020 :Number of voice TCH/F seizure failure. This counter counts the number of TCH/F channel occupation failure during voice channel assignment.After BSC receives the channel request message, it attempts to allocate channel for the request. If occupation fails, this counter accumulates.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource fails, this counter accumulates.If the request returns that the transceiver is faulty, this counter does not change.For failures in other cases, this counter accumulates. C900060030:Number of data TCH/F seizure attempts for assignment. This counter counts the number of TCH/F channel being attempted to be occupied during data channel assignment, including the number of occupation success (C901260070) and the number of occupation failure (C900060031).After BSC receives the channel request massage, it attempts to allocate channel for the request. If allocation and occupation succeed, C900060030 and C901260070 accumulate simultaneously.If occupation fails, C900060030 and C900060031 accumulate simultaneously.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource succeeds, C900060030 and C901260070 accumulate simultaneously. If the waiting for resource fails, C900060030 and C900060031 accumulate simultaneously.If the request returns that the transceiver is faulty, C900060030, C901260070, and C900060031 do not change.For failures in other cases, C900060030 and C900060031 accumulate simultaneously. C900060031:Number of data TCH/F seizure failure for assignment. This counter counts the number of TCH/F channel occupation failure during data channel assignment.After BSC receives the channel request message, it attempts to allocate channel for the request. If occupation fails, this counter accumulates.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource fails, this counter accumulates.If the request returns that the transceiver is faulty, this counter does not change.For failures in other cases, this counter accumulates. C900060042:Number of voice TCH/H seizure attempts for assignmentDescriptionThis counter counts the number of TCH/H channel being attempted to be occupied during voice channel assignment, including the number of occupation success (C901270021) and the number of occupation failure (C900060043).After BSC receives the channel request massage, it attempts to allocate channel for the request. If allocation and occupation succeed, C900060042 and C901270021 accumulate simultaneously.If occupation fails, C900060042 and C900060043 accumulate simultaneously.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource succeeds, C900060042 and C901270021 accumulate simultaneously. If the waiting for resource fails, C900060042 and C900060043 accumulate simultaneously.If the request returns that the transceiver is faulty, C900060042, C901270021, and C900060043 do not change.For failures in other cases, C900060042 and C900060043 accumulate simultaneously. C900060043:Number of voice TCH/H seizure failure for assignmentDescriptionThis counter counts the number of TCH/H channel occupation failure during voice channel assignment.After BSC receives the channel request message, it attempts to allocate channel for the request. If occupation fails, this counter accumulates.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource fails, this counter accumulates.If the request returns that the transceiver is faulty, this counter does not change.For failures in other cases, this counter accumulates. C900060046:Number of data TCH/H seizure attempts for assignmentDescriptionThis counter counts the number of TCH/H channel being attempted to be occupied during data channel assignment, including the number of occupation success (C901270070) and the number of occupation failure (C900060047).After BSC receives the channel request massage, it attempts to allocate channel for the request. If allocation and occupation succeed, C900060046 and C901270070 accumulate simultaneously.If occupation fails, C900060046 and C900060047 accumulate simultaneously.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource succeeds, C900060046 and C901270070 accumulate simultaneously. If the waiting for resource fails, C900060046 and C900060047 accumulate simultaneously.If the request returns that the transceiver is faulty, C900060046, C901270070, and C900060047 do not change.For failures in other cases, C900060046 and C900060047 accumulate simultaneously. C900060047:Number of data TCH/H seizure failure for assignmentDescriptionThis counter counts the number of TCH/H channel occupation failure during data channel assignment.After BSC receives the channel request message, it attempts to allocate channel for the request. If occupation fails, this counter accumulates.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource fails, this counter accumulates.If the request returns that the transceiver is faulty, this counter does not change.For failures in other cases, this counter accumulates. C900060032:Number of data TCH/F seizure attempts for handoverDescriptionThis counter counts the number of TCH/F channel being attempted to be occupied during data channel handover, including the number of occupation success (C901260073) and the number of occupation failure (C900060033).After BSC receives the channel request massage, it attempts to allocate channel for the request. If allocation and occupation succeed, C900060032 and C901260073 accumulate simultaneously.If occupation fails, C900060032 and C900060033 accumulate simultaneously.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource succeeds, C900060032 and C901260073 accumulate simultaneously. If the waiting for resource fails, C900060032 and C900060033 accumulate simultaneously.If the request returns that the transceiver is faulty, C900060032, C901260073, and C900060033 do not change.For failures in other cases, C900060032 and C900060033 accumulate simultaneously. C900060033:Number of data TCH/F seizure failure for handoverDescriptionThis counter counts the number of TCH/F channel occupation failure during data channel handover.After BSC receives the channel request message, it attempts to allocate channel for the request. If occupation fails, this counter accumulates.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource fails, this counter accumulates.If the request returns that the transceiver is faulty, this counter does not change.For failures in other cases, this counter accumulates. C900060044:Number of voice TCH/H seizure attempts for handoverDescriptionThis counter counts the number of TCH/H channel being attempted to be occupied during voice channel handover, including the number of occupation success (C901270024) and the number of occupation failure (C900060045).After BSC receives the channel request massage, it attempts to allocate channel for the request. If allocation and occupation succeed, C900060044 and C901270024 accumulate simultaneously.If occupation fails, C900060044 and C900060045 accumulate simultaneously.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource succeeds, C900060044 and C901270024 accumulate simultaneously. If the waiting for resource fails, C900060044 and C900060045 accumulate simultaneously.If the request returns that the transceiver is faulty, C900060044, C901270024, and C900060045 do not change.For failures in other cases, C900060044 and C900060045 accumulate simultaneously. C900060045:Number of voice TCH/H seizure failure for handoverDescriptionThis counter counts the number of TCH/H channel occupation failure during voice channel handover.After BSC receives the channel request message, it attempts to allocate channel for the request. If allocation or occupation fails, this counter accumulates.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource fails, this counter accumulates.If the request returns that the transceiver is faulty, this counter does not change.For failures in other cases, this counter accumulates. C900060048:Number of data TCH/H seizure attempts for handoverDescriptionThis counter counts the number of TCH/H channel being attempted to be occupied during data channel handover, including the number of occupation success (C901270073) and the number of occupation failure (C900060049).After BSC receives the channel request massage, it attempts to allocate channel for the request. If allocation and occupation succeed, C900060048 and C901270073 accumulate simultaneously.If occupation fails, C900060048 and C900060049 accumulate simultaneously.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource succeeds, C900060048 and C901270073 accumulate simultaneously. If the waiting for resource fails, C900060048 and C900060049 accumulate simultaneously.If the request returns that the transceiver is faulty, C900060048, C901270073, and C900060049 do not change.For failures in other cases, C900060048 and C900060049 accumulate simultaneously. C900060049:Number of data TCH/H seizure failure for handoverDescriptionThis counter counts the number of TCH/H channel occupation failure during data channel handover.After BSC receives the channel request message, it attempts to allocate channel for the request. If occupation fails, this counter accumulates.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource fails, this counter accumulates.If the request returns that the transceiver is faulty, this counter does not change.For failures in other cases, this counter accumulates. C900060017:Number of signaling TCH/F assignment success for assignmentDescriptionThis counter counts the number of successful assignments of TCH/F as signaling channel.After BSC responds the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F. For immediate assignment, after the TCH/F activation succeeds, BTS finds the MS accessed and sends the EST_IND message to BSC, this counter accumulates when BSC receives the message correctly.C900060028:Number of voice TCH/F assignment successDescriptionThis counter counts the number of successful assignments of TCH/F as voice channel.After BSC responds the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F. For assignment from A-interface, after BSC receives the assignment success message, the counter accumulates.C900060036:Number of data TCH/F assignment successDescriptionThis counter counts the number of successful assignments of TCH/F as data channel.After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F. For assignment from A-interface, after BSC receives the assignment success message, the counter accumulates.C900060235:Number of signaling TCH/H assignment successDescriptionThis counter counts the number of successfully assigning TCH/H channel as signaling channel. After BSC responds the channel request and successfully allocates and occupies the channel, BSC sends channel activation message CHL_ACT to activate the TCH/H. For immediate assignment, after the channel activation succeeds, BTS receives the MS access message and sends EST_IND to BSC. The counter increments when BSC receives the message correctly.C900060199:Number of Voice TCH/H assignment successDescriptionThis counter counts the number of successful assignments of TCH/H as voice channel.After BSC responds the channel request message to allocate and occupy TCH/H channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/H. For assignment from A-interface, after BSC receives the assignment success message, the counter accumulates.C900060210:Number of data TCH/H assignment successDescriptionThis counter counts the number of successful assignments of TCH/H as data channel.After BSC responds to the channel request message to allocate and occupy TCH/H channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/H. For assignment from A-interface, after BSC receives the assignment success message, the counter accumulates.C900060211:Number of data TCH/H assignment failureDescriptionThis counter counts the number of failing to assign TCH/H channel as data channel.After BSC responds to the channel request message to allocate and occupy TCH/H channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/H. If BSC does not receive the MS access notification within a certain time, this assignment fails.C900060200:Number of Voice TCH/H assignment failureDescriptionThis counter counts the number of failing to assign TCH/H channel as voice channel.After BSC responds to the channel request message to allocate and occupy TCH/H channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/H. If BSC does not receive the MS access notification within a certain time, this assignment fails.C900060135:Number of signaling TCH/H assignment failureDescriptionThis counter counts the number of failing to assign TCH/H channel as a signaling channel. After BSC responds to the channel request message to allocate and occupy TCH/H successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/H. If BSC does not receive the MS access notification within a certain time, this assignment fails.C900060037:Number of data TCH/F assignment failureDescriptionThis counter counts the number of failing to assign TCH/F channel as data channel.After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F. If BSC does not receive the MS access notification within a certain time, this assignment fails.C900060029:Number of voice TCH/F assignment failure for assignmentDescriptionThis counter counts the number of failing to assign TCH/F channel as voice channel.After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F. If BSC does not receive the MS access notification within a certain time, this assignment fails.C900060018:Number of signaling TCH/F assignment failure for assignmentDescriptionThis counter counts the number of failing to assign TCH/F channel as signaling channel.After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F. If BSC does not receive the MS access notification within a certain time, this assignment fails.C900060020:Number of voice TCH/F seizure failureDescriptionThis counter counts the number of TCH/F channel occupation failure during voice channel assignment.After BSC receives the channel request message, it attempts to allocate channel for the request. If occupation fails, this counter accumulates.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource fails, this counter accumulates.If the request returns that the transceiver is faulty, this counter does not change.For failures in other cases, this counter accumulates. C900060031:Number of data TCH/F seizure failure for assignmentDescriptionThis counter counts the number of TCH/F channel occupation failure during data channel assignment.After BSC receives the channel request message, it attempts to allocate channel for the request. If occupation fails, this counter accumulates.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource fails, this counter accumulates.If the request returns that the transceiver is faulty, this counter does not change.For failures in other cases, this counter accumulates. C900060043:Number of voice TCH/H seizure failure for assignmentDescriptionThis counter counts the number of TCH/H channel occupation failure during voice channel assignment.After BSC receives the channel request message, it attempts to allocate channel for the request. If occupation fails, this counter accumulates.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource fails, this counter accumulates.If the request returns that the transceiver is faulty, this counter does not change.For failures in other cases, this counter accumulates. C900060047:Number of data TCH/H seizure failure for assignmentDescriptionThis counter counts the number of TCH/H channel occupation failure during data channel assignment.After BSC receives the channel request message, it attempts to allocate channel for the request. If occupation fails, this counter accumulates.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource fails, this counter accumulates.If the request returns that the transceiver is faulty, this counter does not change.For failures in other cases, this counter accumulates. C900060019:Number of voice TCH/F seizure attemptsDescriptionThis counter counts the number of TCH/F channel being attempted to be occupied during voice channel assignment, including the number of occupation success (C901260021) and the number of occupation failure (C900060020).After BSC receives the channel request massage, it attempts to allocate channel for the request. If allocation and occupation succeed, C900060019 and C901260021 accumulate simultaneously.If occupation fails, C900060019 and C900060020 accumulate simultaneously.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource succeeds, C900060019 and C901260021 accumulate simultaneously. If the waiting for resource fails, C900060019 and C900060020 accumulate simultaneously.If the request returns that the transceiver is faulty, C900060019, C901260021, and C900060020 do not change.For failures in other cases, C900060019 and C900060020 accumulate simultaneously. C900060030:Number of data TCH/F seizure attempts for assignmentDescriptionThis counter counts the number of TCH/F channel being attempted to be occupied during data channel assignment, including the number of occupation success (C901260070) and the number of occupation failure (C900060031).After BSC receives the channel request massage, it attempts to allocate channel for the request. If allocation and occupation succeed, C900060030 and C901260070 accumulate simultaneously.If occupation fails, C900060030 and C900060031 accumulate simultaneously.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource succeeds, C900060030 and C901260070 accumulate simultaneously. If the waiting for resource fails, C900060030 and C900060031 accumulate simultaneously.If the request returns that the transceiver is faulty, C900060030, C901260070, and C900060031 do not change.For failures in other cases, C900060030 and C900060031 accumulate simultaneously. C900060042:Number of voice TCH/H seizure attempts for assignmentDescriptionThis counter counts the number of TCH/H channel being attempted to be occupied during voice channel assignment, including the number of occupation success (C901270021) and the number of occupation failure (C900060043).After BSC receives the channel request massage, it attempts to allocate channel for the request. If allocation and occupation succeed, C900060042 and C901270021 accumulate simultaneously.If occupation fails, C900060042 and C900060043 accumulate simultaneously.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource succeeds, C900060042 and C901270021 accumulate simultaneously. If the waiting for resource fails, C900060042 and C900060043 accumulate simultaneously.If the request returns that the transceiver is faulty, C900060042, C901270021, and C900060043 do not change.For failures in other cases, C900060042 and C900060043 accumulate simultaneously. C900060046:Number of data TCH/H seizure attempts for assignmentDescriptionThis counter counts the number of TCH/H channel being attempted to be occupied during data channel assignment, including the number of occupation success (C901270070) and the number of occupation failure (C900060047).After BSC receives the channel request massage, it attempts to allocate channel for the request. If allocation and occupation succeed, C900060046 and C901270070 accumulate simultaneously.If occupation fails, C900060046 and C900060047 accumulate simultaneously.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource succeeds, C900060046 and C901270070 accumulate simultaneously. If the waiting for resource fails, C900060046 and C900060047 accumulate simultaneously.If the request returns that the transceiver is faulty, C900060046, C901270070, and C900060047 do not change.For failures in other cases, C900060046 and C900060047 accumulate simultaneously. C900060022:Number of voice TCH/F seizure failure for handoverDescriptionThis counter counts the number of TCH/F channel occupation failure during voice channel handover.After BSC receives the channel request message, it attempts to allocate channel for the request. If allocation or occupation fails, this counter accumulates.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource fails, this counter accumulates.If the request returns that the transceiver is faulty, this counter does not change.For failures in other cases, this counter accumulates. C900060033:Number of data TCH/F seizure failure for handoverDescriptionThis counter counts the number of TCH/F channel occupation failure during data channel handover.After BSC receives the channel request message, it attempts to allocate channel for the request. If occupation fails, this counter accumulates.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource fails, this counter accumulates.If the request returns that the transceiver is faulty, this counter does not change.For failures in other cases, this counter accumulates. C900060045:Number of voice TCH/H seizure failure for handoverDescriptionThis counter counts the number of TCH/H channel occupation failure during voice channel handover.After BSC receives the channel request message, it attempts to allocate channel for the request. If allocation or occupation fails, this counter accumulates.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource fails, this counter accumulates.If the request returns that the transceiver is faulty, this counter does not change.For failures in other cases, this counter accumulates. C900060049:Number of data TCH/H seizure failure for handoverDescriptionThis counter counts the number of TCH/H channel occupation failure during data channel handover.After BSC receives the channel request message, it attempts to allocate channel for the request. If occupation fails, this counter accumulates.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource fails, this counter accumulates.If the request returns that the transceiver is faulty, this counter does not change.For failures in other cases, this counter accumulates. C900060021:Number of voice TCH/F seizure attempts for handoverDescriptionThis counter counts the number of TCH/F channel being attempted to be occupied during voice channel handover, including the number of occupation success (C901260024) and the number of occupation failure (C900060022).After BSC receives the channel request massage, it attempts to allocate channel for the request. If allocation and occupation succeed, C900060021 and C901260024 accumulate simultaneously.If occupation fails, C900060021 and C900060022 accumulate simultaneously.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource succeeds, C900060021 and C901260024 accumulate simultaneously. If the waiting for resource fails, C900060021 and C900060022 accumulate simultaneously.If the request returns that the transceiver is faulty, C900060021, C901260024, and C900060022 do not change.For failures in other cases, C900060021 and C900060022 accumulate simultaneously. C900060032:Number of data TCH/F seizure attempts for handoverDescriptionThis counter counts the number of TCH/F channel being attempted to be occupied during data channel handover, including the number of occupation success (C901260073) and the number of occupation failure (C900060033).After BSC receives the channel request massage, it attempts to allocate channel for the request. If allocation and occupation succeed, C900060032 and C901260073 accumulate simultaneously.If occupation fails, C900060032 and C900060033 accumulate simultaneously.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource succeeds, C900060032 and C901260073 accumulate simultaneously. If the waiting for resource fails, C900060032 and C900060033 accumulate simultaneously.If the request returns that the transceiver is faulty, C900060032, C901260073, and C900060033 do not change.For failures in other cases, C900060032 and C900060033 accumulate simultaneously. C900060044:Number of voice TCH/H seizure attempts for handoverDescriptionThis counter counts the number of TCH/H channel being attempted to be occupied during voice channel handover, including the number of occupation success (C901270024) and the number of occupation failure (C900060045).After BSC receives the channel request massage, it attempts to allocate channel for the request. If allocation and occupation succeed, C900060044 and C901270024 accumulate simultaneously.If occupation fails, C900060044 and C900060045 accumulate simultaneously.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource succeeds, C900060044 and C901270024 accumulate simultaneously. If the waiting for resource fails, C900060044 and C900060045 accumulate simultaneously.If the request returns that the transceiver is faulty, C900060044, C901270024, and C900060045 do not change.For failures in other cases, C900060044 and C900060045 accumulate simultaneously. C900060048:Number of data TCH/H seizure attempts for handoverDescriptionThis counter counts the number of TCH/H channel being attempted to be occupied during data channel handover, including the number of occupation success (C901270073) and the number of occupation failure (C900060049).After BSC receives the channel request massage, it attempts to allocate channel for the request. If allocation and occupation succeed, C900060048 and C901270073 accumulate simultaneously.If occupation fails, C900060048 and C900060049 accumulate simultaneously.If the request returns no channel available but queuing or forced release is possible, enter the state of waiting for resource. If the waiting for resource succeeds, C900060048 and C901270073 accumulate simultaneously. If the waiting for resource fails, C900060048 and C900060049 accumulate simultaneously.If the request returns that the transceiver is faulty, C900060048, C901270073, and C900060049 do not change.For failures in other cases, C900060048 and C900060049 accumulate simultaneously. C900060017:Number of signaling TCH/F assignment success for assignmentDescriptionThis counter counts the number of successful assignments of TCH/F as signaling channel.After BSC responds the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F. For immediate assignment, after the TCH/F activation succeeds, BTS finds the MS accessed and sends the EST_IND message to BSC, this counter accumulates when BSC receives the message correctly.C900060028:Number of voice TCH/F assignment successDescriptionThis counter counts the number of successful assignments of TCH/F as voice channel.After BSC responds the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F. For assignment from A-interface, after BSC receives the assignment success message, the counter accumulates.C900060036:Number of data TCH/F assignment successDescriptionThis counter counts the number of successful assignments of TCH/F as data channel.After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F. For assignment from A-interface, after BSC receives the assignment success message, the counter accumulates.C900060235:Number of signaling TCH/H assignment successDescriptionThis counter counts the number of successfully assigning TCH/H channel as signaling channel. After BSC responds the channel request and successfully allocates and occupies the channel, BSC sends channel activation message CHL_ACT to activate the TCH/H. For immediate assignment, after the channel activation succeeds, BTS receives the MS access message and sends EST_IND to BSC. The counter increments when BSC receives the message correctly.C900060199:Number of Voice TCH/H assignment successDescriptionThis counter counts the number of successful assignments of TCH/H as voice channel.After BSC responds the channel request message to allocate and occupy TCH/H channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/H. For assignment from A-interface, after BSC receives the assignment success message, the counter accumulates.C900060210:Number of data TCH/H assignment successDescriptionThis counter counts the number of successful assignments of TCH/H as data channel.After BSC responds to the channel request message to allocate and occupy TCH/H channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/H. For assignment from A-interface, after BSC receives the assignment success message, the counter accumulates.C900060018:Number of signaling TCH/F assignment failure for assignmentDescriptionThis counter counts the number of failing to assign TCH/F channel as signaling channel.After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F. If BSC does not receive the MS access notification within a certain time, this assignment fails.C900060029:Number of voice TCH/F assignment failure for assignmentDescriptionThis counter counts the number of failing to assign TCH/F channel as voice channel.After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F. If BSC does not receive the MS access notification within a certain time, this assignment fails.C900060037:Number of data TCH/F assignment failureDescriptionThis counter counts the number of failing to assign TCH/F channel as data channel.After BSC responds to the channel request message to allocate and occupy TCH/F channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/F. If BSC does not receive the MS access notification within a certain time, this assignment fails.C900060135:Number of signaling TCH/H assignment failureDescriptionThis counter counts the number of failing to assign TCH/H channel as a signaling channel. C900060200:Number of Voice TCH/H assignment failureDescriptionThis counter counts the number of failing to assign TCH/H channel as voice channel.After BSC responds to the channel request message to allocate and occupy TCH/H channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/H. If BSC does not receive the MS access notification within a certain time, this assignment fails.C900060211:Number of data TCH/H assignment failureDescriptionThis counter counts the number of failing to assign TCH/H channel as data channel.After BSC responds to the channel request message to allocate and occupy TCH/H channel successfully, BSC sends the CHL_ACT message to BTS to activate this TCH/H. If BSC does not receive the MS access notification within a certain time, this assignment fails.C900060093:Number of BSC-controlled inter-cell outgoing handoverDescriptionThis counter counts the number of intra-BSC inter-cell handover-out executions. The execution here means the radio resource of target cell has been successfully requested, and system returns the message of radio resource available.UsageThis counter is used to find out the frequency of intra-BSC inter-cell outgoing handover execution. It is one of the parameters that evaluate radio environment, and it reflects the handover situation. Measurement PointDuring the handover process, if the target cell requests for channel successfully, it sends the message of radio resource available back to the source cell. The source cell performs judgment after receiving the message. If the request is due to intra-BSC inter-cell handover, this counter increments. C900060094:Number of BSC-controlled inter-cell outgoing handover successDescriptionThis counter counts the number of successful intra-BSC inter-cell outgoing handovers.UsageThis counter is used to find out the frequency of successful intra-BSC inter-cell outgoing handover. It is one of the parameters that evaluate the handover situation.Measurement PointDuring the handover process, when the source cell receives the handover completion message from the target cell, it indicates that MS has accessed the target channel and handover succeeds. In this case, this counter increments. C900060095:Number of MSC-controlled outgoing handoverDescriptionThis counter counts the number of MSC-controlled inter-BSC outgoing handover executions.UsageThis counter is used to find out the frequency of MSC-controlled inter-BSC outgoing handover execution, and it reflects the handover situation.Measurement PointBSC performs handover decision after receiving MS measurement report. If the handover decision indicates inter-cell handover and the currently attempted cell is a cell under another BSC, the source BSC sends the handover request message A_HO_RQD to MSC to trigger inter-BSC handover. If the source BSC receives the handover command returned from MSC, the counter increments. C900060096:Number of MSC-controlled outgoing handover successDescriptionThis counter counts the number of successful MSC-controlled inter-BSC outgoing handovers.UsageThis counter is used to find out the frequency of successful MSC-controlled inter-BSC outgoing handover, and it reflects the handover situation.Measurement PointBSC performs handover decision after receiving MS measurement report. If the handover decision indicates inter-cell handover and the currently attempted cell is a cell under another BSC, the source BSC sends the handover request message A_HO_RQD to MSC to trigger inter-BSC handover. If MS successfully accesses the target cell, the source cell receives the release command issued by MSC. In this case, this counter increments. C900060097:Number of BSC-controlled inter-cell incoming handoverDescriptionThis counter counts the number of BSC-controlled inter-cell incoming handover executions.UsageThis counter is used to find out the frequency of BSC-controlled inter-cell incoming handover execution. It is one of the parameters that evaluate radio environment, and it reflects the handover situation. Measurement PointIf channel activation succeeds in the target cell within BSC and the request is due to inter-cell handover, the counter increments. C900060098Number of BSC-controlled inter-cell incoming handover successDescriptionThis counter counts the number of successful BSC-controlled inter-cell incoming handovers.UsageThis counter shows the frequency of successful BSC-controlled inter-cell incoming handover, and it reflects the handover situation.Measurement PointWhen the target cell within BSC receives the handover completion message, if the request is due to BSC-controlled inter-cell handover, the counter increments. :C900060099:Number of MSC-controlled incoming handoverDescriptionThis counter counts the number of MSC-controlled inter-BSC incoming handover executions.UsageThis counter is used to find out the frequency of MSC-controlled inter-BSC incoming handover executions. It is one of the parameters that evaluate radio environment, and it reflects the handover situation. Measurement PointAfter the target cell receives the handover request message issued by MSC, the counter increments if the channel is allocated and activated successfully. C900060100:Number of MSC-controlled incoming handover due to forced releaseDescriptionDuring MSC-controlled inter-BSC incoming handover process, the counter counts the number of forced release executions due to no available radio resource in the target cell.UsageThis counter is used to find out the frequency of forced release executions during MSC-controlled inter-BSC incoming handover process. It reflects the handover situation. Measurement PointThe target cell receives the radio channel request message. If the request is due to MSC-controlled inter-BSC incoming handover and the target cell has no available radio channels, forced release is attempted. If the target cell receives the message of resource available returned by the forced release instance, the counter increments. C900060101:Number of MSC-controlled incoming handover due to queueDescriptionDuring MSC-controlled inter-BSC incoming handover process, the counter counts the number of queuing executions due to no available radio resource in the target cell.UsageThis counter is used to find out the frequency of queuing executions during MSC-controlled inter-BSC incoming handover process, and it reflects the handover situation. Measurement PointThe target cell receives the radio channel request message. If the request is due to MSC-controlled inter-BSC incoming handover and the target cell has no available radio channels, the target instance is added to the waiting queue. When the target cell receives the message of resource available, the counter increments. C900060102:Number of MSC-controlled incoming handover successDescriptionThis counter counts the number of successful MSC-controlled inter-BSC incoming handovers.UsageThis counter is used to find out the frequency of successful MSC-controlled inter-BSC incoming handover, and it reflects the handover situation. Measurement PointWhen the target cell receives the handover completion message, if the request is due to MSC-controlled inter-BSC incoming handover, the counter increments. C900060119:Number of Intra-cell handoverDescriptionThis counter counts the number of intra-cell handover executions which is initiated by MS in the source cell. Here, the execution means that radio resource is requested successfully and the message of resource