【正文】 EDIATE ASSIGNMENT REJECTALLOC_SDCCH_FAILCHAN_REQ_MS_BLKIMMEDIATE ASSIGNMENT(AGCH)ALLOC_SDCCHCHAN_REQ_MS_FAIL(TIME OUT)rr_t3101SABM+INITIAL LAY3 MESSAGE(SD)OK_ACC_PROC[CM ]or [CM REESTABLISHMENT]or [PAGE RESPONSE]or [LOCATION UPDATE]or [IMSI DETACH]CONNECTION REQUEST CRCONN_REQ_TO_MSCCONNECTION CONFIRM CC ORCONNECTION REFUSED CREFCONN_REFUEDASSIGNMENT REQUESTMA_REQ_FROM_MSCALLOC_TCH_FAILMA_CMD_TO_MS_BLKDALLOC_TCHASSIGNMENT COMMAND(SDCCH)MA_CMD_TO_MSASSIGNMENT FAILURE(SDCCH)MA_FAIL_FROM_MSASSIGNMENT FAILUREASSIGNMENT COMPLETE(TCH)ASSIGNMENT COMPLETETOTAL_CALLSMA_COMPLETE_TO_MSCMSBSSMSC④BSC向MSC發(fā)出建立呼叫的請求，MSC向BSC回送一條SCCP連接拒絕消息，這種情況統(tǒng)計在CONN_REFUSED（位于SSM）中,若該項(xiàng)數(shù)據(jù)值過大，表明BSC和MSC之間的信令配合有問題。⑥BSC通過SDCCH向MS發(fā)出一條分配TCH的消息，MS在SDCCH上回送一分配失敗消息，BSC再把該消息送到MSC，呼叫建立失敗。MS做被叫時多一尋呼過程，隨后的過程與主叫相同，如下頁所示。后一個階段我們有統(tǒng)計數(shù)據(jù)呼叫建立成功率（Call_Setup_Success_Rate）、TCH阻塞率（TCH_CONGESTION_KEY）、TCH分配失敗丟失率（ASSIGN_FAILURE_RATE_LOST）和TCH分配失敗恢復(fù)率（ASSIGN_FAILURE_RATE_RECONER）；前一個階段我們除了一些統(tǒng)計項(xiàng)，如SDCCH射頻丟失率（SDCCH_RF_LOSS_RATE）、SDCCH阻塞率（SDCCH_CONGESTION_KEY）外，還可以自己組合一些原始統(tǒng)計數(shù)據(jù)來分析小區(qū)的SDCCH接入性能。計算公式如下：ASSIGN_FAILURE_RATE_LOST(%)= TCH分配失敗恢復(fù)率（ASSIGN_FAILURE_RATE_RECOVER）：表示BTS發(fā)出分配命令（Assignment Commands）給MS，但MS未能到達(dá)分配TCH返回到原SDCCH，并將分配失?。ˋssignament failure）消息返回給BTS所占的比例。Page: 32還有數(shù)據(jù)庫參數(shù)的設(shè)置，rr_t3101計算公式如下：SDCCH_ACCESS_RATE(%)=CIC分配成功率（CIC_ALLOC_SUC_RATE）：表示交換機(jī)向BSS發(fā)送分配請求（建立TCH）占所有需建立TCH（MS主叫、MS被叫和呼叫重建）的呼叫請求的比例。分析流程圖呼叫建立成功率分析：CONN_REFUSED是否異常，MSC方面有無阻塞及其它問題，如屬信令配合問題與MSC工程師協(xié)商解決同一MSC下小區(qū)是否正常？不正常正常檢查CIC分配成功率同一BSC下小區(qū)是否正常？該小區(qū)的TCH阻塞率正常否？不正常降低小區(qū)TCH阻塞（見下面的TCH阻塞分析）某小區(qū)的呼叫建立成功率偏低不正常正常不正常正常是否有CIC阻塞及檢查BSC方面A接口參數(shù)設(shè)置及硬件檢查BSC方面A接口參數(shù)設(shè)置及硬件降低小區(qū)的SDCCH射頻丟失率，參見下面掉話分析檢查小區(qū)的SDCCH射頻丟失率值路測檢查小區(qū)的覆蓋、信號電平、干擾情況、下站檢查硬件問題，檢查小區(qū)數(shù)據(jù)庫等不正常正常不正常正常不正常正常降低小區(qū)的SDCCH射頻丟失率，參見下面掉話分析檢查小區(qū)的TCH分配丟失率和恢復(fù)率正常不正常更換MCU（GPROC）、TCU等SDCCH性能分析：小區(qū)的SDCCH阻塞率過高降低小區(qū)SDCCH阻塞（見下面的SDCCH阻塞分析）小區(qū)的SDCCH接入率過低更換SDCCH所在載頻檢查小區(qū)的SDCCH射頻丟失率值檢查數(shù)據(jù)庫參數(shù)設(shè)置特別是rr_t3101等定時器參數(shù)降低小區(qū)的SDCCH射頻丟失率，參見下面掉話分析（4）阻塞分析阻塞率和掉話率是我們?nèi)粘＞S護(hù)和優(yōu)化中最關(guān)心的兩個指標(biāo)。下面針對每種情況進(jìn)行分析。③SDCCH阻塞高，而TCH阻塞低或無阻塞。系統(tǒng)內(nèi)各小區(qū)T3212 應(yīng)一致。取值范圍0－3。SDCCH和TCH均阻塞：其它情況正常偏高位置更新次數(shù)是否偏高偏高正常SDCCH上的干擾與射頻丟失情況如何降低小區(qū)的SDCCH射頻丟失率，參見下面掉話分析小區(qū)的SDCCH阻塞TCH無阻塞率鄰小區(qū)的阻塞率正常否本小區(qū)加載頻或在小區(qū)方向上增加基站偏高正常降低小區(qū)的SDCCH射頻丟失率，參見下面掉話分析調(diào)整天線、修改切換門限、調(diào)整小區(qū)選擇參數(shù)、小區(qū)重新配置與鄰小區(qū)均衡業(yè)務(wù)量小區(qū)的SDCCH和TCH阻塞率均高SDCCH無阻塞，TCH阻塞的情況與兩者均阻塞處理方法類似。而根據(jù)TCH掉話率的公式（見前面常用指標(biāo)數(shù)據(jù)），我們可將其分為兩部分：射頻丟失率（TCH_RF_LOSS_RATE）和切換丟失率組成的（HO_LOSS_RATE），如下所示（以小區(qū)統(tǒng)計為例）：射頻丟失率：切換丟失率：因此對掉話的分析可分別從RF LOSS問題和HO LOSS問題著手。；干擾問題可通過觀察 intf_on_idle、BER等統(tǒng)計數(shù)據(jù)來發(fā)現(xiàn)解決Page: 38過高的基站減小BTS POWER后，可能下行信號質(zhì)量會有改善，但intf_on_idle、tch_rf_loss可能會較大。切換邊界不合理指切換邊界設(shè)置在MS頻繁移動的地方，如繁華道路、商場等區(qū)域，由于在邊界處幾個小區(qū)信號電平相差無幾，無主導(dǎo)小區(qū)，MS頻繁切換，容易導(dǎo)致切換掉話，可采用調(diào)整天線傾角和高度、BTS發(fā)射功率等方法，使切換邊界避開MS頻繁移動區(qū)域；切換問題包括鄰小區(qū)表問題、鄰小區(qū)阻塞問題、切換速度問題。過低的切換速度會導(dǎo)致射頻丟失,過快的切換速度會導(dǎo)致切換失敗甚至是切換掉話，可通過調(diào)整相應(yīng)的數(shù)據(jù)庫參數(shù)來解決Page: 38Hreqave；hreqt；n/p；threshold；軟件錯誤是指由于一些控制呼叫進(jìn)程的軟件出現(xiàn)問題導(dǎo)致的掉話，如當(dāng)小區(qū)的切換進(jìn)程處于休眠狀態(tài)，則該小區(qū)無切換發(fā)生，會有較高的TCH_RF_LOSS_RATE，可通過INS或更換 DRIs、MCU等方法解決；數(shù)據(jù)庫中某些參數(shù)的設(shè)置錯誤也會導(dǎo)致非正常的掉話，解決方法是設(shè)置合適的參數(shù)。TOP20方法基于以下理由：① 各項(xiàng)統(tǒng)計數(shù)據(jù)內(nèi)在是密切相關(guān)的。③ 便于發(fā)現(xiàn)主要矛盾，處理問題嚴(yán)重的小區(qū)。這樣，我們就可以較為容易地各項(xiàng)數(shù)據(jù)關(guān)聯(lián)起來，發(fā)現(xiàn)規(guī)律，找出問題。由于SDCCH存在較強(qiáng)的干擾，移動臺無法占用該SDCCH載頻，或者占用該SDCCH后，發(fā)生SDCCH的掉話。題目：1． 說出六種統(tǒng)計數(shù)據(jù)類型。附錄 ESTSG32 附錄一：呼叫處理階梯圖Connection establishmentSuccessful (mobile originated)Figure 11 shows a successful mobile generated connection establishment. Figure 11 Connection establishment successfulFailureFigure 12 shows a connection establishment failure: Figure 12 Connection establishment failureImmediate assignment blockedFigure 13 shows an immediate assignment blocked: Figure 13 Immediate assignment blockedImmediate assignment failureFigure 14 shows an immediate assignment failure: Figure 14 Immediate assignment failureSuccessful mobile terminated callFigure 15 shows a connection establishment (mobile terminated call) successful. Figure 15 Connection establishment (mobile terminated call) successfulAssignment to TCHAssignment successfulFigure 21 shows a successful TCH assignment: Figure 21 TCH assignment successfulImmediate assignment failureFigure 22 shows an immediate assignment failure: Figure 22 Immediate assignment failureTCH assignment blockedFigure 23 shows a TCH assignment blocked: Figure 23 TCH assignment blockedFail recoveredFigure 24 shows a TCH assignment failrecovered to a SDCCH: Figure 24 TCH assignment failrecovered to SDCCHIntracell handoverHandover successfulFigure 31 shows a successful intracell handover: Figure 31 Handover (intracell) successfulHandover blockedFigure 32 shows an intracell handover blocked: Figure 32 Handover (intracell) blockedFail recoveredFigure 33 shows an intracell handover failrecovered to a source channel: Figure 33 Handover (intracell) failrecovered to source channelFail lostFigure 34 shows an intracell handover faillost: Figure 34 Handover (intracell) faillostInterBSS handoverHandover successfulFigure 41 shows a successful interBSS handover: Figure 41 Handover (interBSS) successfulHandover blockedFigure 42 shows an interBSS handover blocked: Figure 42 Handover (interBSS) blockedFail recoveredFigure 43 shows an interBSS handover failrecovered: Figure 43 Handover (interBSS) failrecoveredFail lostFigure 44 shows an interBSS handover faillost: Figure 44 Handover (interBSS) faillostFail lost (mobi