【文章內(nèi)容簡介】 Lack of bandwidth on the Iub C602 注：這兩個(gè) counter 統(tǒng)計(jì)的是 RAB Assignment 過程當(dāng)中不同階段的問題。 RadioBearerEstablishmentUnsuccess 主要統(tǒng)計(jì)在 RB setup Request 發(fā)出去之前 RadioBearerSetupUnsuccess統(tǒng)計(jì)的是在 RB setup Request發(fā)出之后直到 RNC回復(fù) RAB Assignment Response C670 Screening 0 Descr.: Unavailable DL code resources Screening 1 Descr.: Unavailable DL power resources Screening 2 Descr.: Unspecified Screening 3 Descr.: CAC RNC Processing resources Screening 4 Descr.: Lack of bandwidth on the Iu Screening 5 Descr.: Lack of bandwidth on the Iur Screening 6 Descr.: Lack of bandwidth on the Iub RL 建立失敗的分析 如果發(fā)現(xiàn) RL 建立失敗，我們主要通過如下如下 counter 進(jìn)行統(tǒng)計(jì)： C38 Screening 0 Descr.: RADIO_LINK_SETUP_FAILURE Screening 1 Descr.: Timeout Screening 2 Descr.: Rrm refusal Screening 3 Descr.: Iub Layer Congestion Screening 4 Descr.: NodeB (CEM) lack of L1 resources Screening 5 Descr.: Lack of Transport Identifier (CID or UDP Port) on the Iub Screening 6 Descr.: Lack of bandwidth on the Iub Screening 7 Descr.: INode refusal Screening 9 Descr.: Multicell Operation Not Available C39 Screening 0 Descr.: RADIO_LINK_ADDITION_FAILURE Screening 1 Descr.: Timeout Screening 2 Descr.: Rrm refusal Screening 3 Descr.: INode refusal Screening 4 Descr.: NodeB (CEM) lack of L1 resources Screening 5 Descr.: Lack of Transport Identifier (CID or UDP Port) on the Iub Screening 6 Descr.: Lack of bandwidth on the Iub Screening 7 Descr.: Iub Layer Congestion C40 Screening 0 Descr.: RADIO_LINK_RECONFIGURATION_FAILURE Screening 1 Descr.: Timeout nbap Screening 2 Descr.: Rrm refusal Screening 3 Descr.: Iub Layer Congestion Screening 4 Descr.: NodeB (CEM) lack of L1 resources Screening 5 Descr.: Lack of Transport Identifier (CID or UDP Port) on the Iub Screening 6 Descr.: Lack of bandwidth on the Iub Screening 7 Descr.: INode refusal Screening 9 Descr.: Multicell Operation not Available 隨后 查詢 RNC COUNTER， 統(tǒng)計(jì)一下話務(wù)報(bào)告 :是否有上行負(fù)荷原因?qū)е碌?RL setup or RL 重配失敗較多次數(shù) ，查詢下面兩個(gè) counter， , 發(fā)現(xiàn)存在這類問題。 優(yōu)化建議關(guān)閉 UL token cac： 參數(shù)路徑 ： RNC/RadioAccessService/isUltokenCatAtRncAllowed: truefalse 這樣可以避免上行 token 受限導(dǎo)致的 RadioLink 建立或重建失敗導(dǎo)致的大量的 RAB 失敗次數(shù) 基于上行負(fù)載的 UL Token Cac 功能是 UA05 以后提供的一個(gè)功能，它通過為高速上行R99 PS業(yè)務(wù)設(shè)置一個(gè) UL Token并 在呼叫準(zhǔn)入的時(shí)候考察該 Token 是否超限來避免上行接入太多高速連接從而導(dǎo)致過高的上行負(fù)荷。該功能開啟后，在呼叫建立時(shí)， RNC會(huì)去判斷 UL Token 是否超限，如果超限則 CAC 失敗，呼叫無法建立。 不同上行業(yè)務(wù)信道的 UL Token 通過參數(shù) RNC/ RadioAccessService/ UlUserService/ ulCostForUlTokenCac 來定義。根據(jù) UPUG 的建議，該參數(shù)的設(shè)置如下： ulCostForUlTokenCac = 0 for UlUserService with SF 8 ulCostForUlTokenCac = 16 for UlUserService with SF = 8（如 PS128） ulCostForUlTokenCac = 48 for UlUserService with SF = 4（如 PS384） 而小區(qū)的總上行 Token 的門限根據(jù) UPUG 建議設(shè)定為： RNC/ NodeB/ FDDCell/ ulCapacityThresholdForUlTokenCac = 120 也就是說如果該功能開啟，上行只能承擔(dān) 個(gè) PS384 或者 個(gè) PS128，這顯然 會(huì)嚴(yán)重影響小區(qū)的接入性能。 所以我們把基于上行負(fù)載的 UL Token Cac 功能 關(guān)閉。 問題發(fā)現(xiàn) 及分析處理 PS R99 業(yè)務(wù) 導(dǎo)致 CE 不足 問題 UL Token Cac功能關(guān)閉 后， RAB 建立指標(biāo)并未有明顯改善， 但 kpi指標(biāo)并無其他資源受限。懷疑是 ps R99用戶過多，占用了較多的 CE 資源，查詢下面 counter中的子 counter： C1666 Screening 0 Descr.: Other Screening 1 Descr.: Signalling Only Screening 2 Descr.: CS speech NB or LR AMR Screening 3 Descr.: CS speech WB AMR Screening 4 Descr.: CS data Screening 5 Descr.: CS Streaming Screening 6 Descr.: CS Streaming Screening 7 Descr.: PS Streaming 16 Screening 8 Descr.: PS Streaming 64 Screening 9 Descr.: PS Streaming 128 Screening 10 Descr.: PS Streaming 256 Screening 11 Descr.: PS Streaming 384 Screening 12 Descr.: PS I/B 0 Screening 13 Descr.: PS I/B 8 Screening 14 Descr.: PS I/B 16 Screening 15 Descr.: PS I/B 32 Screening 16 Descr.: PS I/B 64 Screening 17 Descr.: PS I/B 128 Screening 18 Descr.: PS I/B 256 Screening 19 Descr.: PS I/B 384 Screening 20 Descr.: HSDPA Screening 21 Descr.: TRB on cell FACH Screening 22 Descr.: CS Speech HSDPA Avg 值是錯(cuò)誤的，不用看；可以用 Cum/NbEvt 來代替，表示該占用的 Erl Cum Max重要！代表最大連接數(shù)，可以通過它計(jì)算最大資源消耗 Min NbEvt 應(yīng)該在 36000 左右（每 100ms 上報(bào)一次） C1667 Screening 0 Descr.: Other Screening 1 Descr.: Signalling Only Screening 2 Descr.: CS speech Screening 3 Descr.: CS data Screening 4 Descr.: CS Streaming Screening 5 Descr.: CS Streaming Screening 6 Descr.: PS Streaming 16 Screening 7 Descr.: PS Streaming 32 Screening 8 Descr.: PS Streaming 64 Screening 9 Descr.: PS Streaming 128 Screening 10 Descr.: PS I/B 8 Screening 11 Descr.: PS I/B 16 Screening 12 Descr.: PS I/B 32 Screening 13 Descr.: PS I/B 64 Screening 14 Descr.: PS I/B 128 Screening 15 Descr.: PS I/B 384 Screening 16 Descr.: PS I/B or PS Str HSUPA Screening 17 Descr.: TRB on cell RACH Screening 18 Descr.: CS Speech HSUPA Avg 值是錯(cuò)誤的，不用看；可以用 Cum/NbEvt 來代替，表示該占用的 Erl Cum Max 重要！代表最大連接數(shù)，可以通過它計(jì)算最大資源消耗 Min NbEvt 應(yīng)該在 36000 左右（每 100ms 上報(bào)一次） 終端類型的統(tǒng)計(jì)： 通過 C10825 可以統(tǒng)計(jì)出 UE 的 category。 10825 distribution according to the UE category ? SubCounter 0: For UE category 1 ? SubCounter 1: For UE category 2 ? SubCounter 2: For UE category 3 ? SubCounter 3: For UE category 4 ? SubCounter 4: For UE category 5 ? SubCounter 5: For UE category 6 ? SubCounter 6: For UE category 7 ? SubCounter 7: For UE category 8 ? SubCounter 8: For UE category 9 ? SubCounter 9: For UE category 10 ? SubCounter 10: For UE category 11 ? SubCounter 11: For UE category 12 CQI 的統(tǒng)計(jì)： 通過 C10819 來進(jìn)行 CQI 的統(tǒng)計(jì) 10819 distribution according CQI SubCounter 0: For level 0 SubCounter 1: For level 1 SubCounter 2: For level 2 SubCounter 3: For level 3 SubCounter 4: For level 4 SubCounter 5: For level 5 SubCounter 6: For level 6 SubCounter 7: For level 7 SubCounter 8: For level 8 SubCounter 9: For level 9 SubCounter 10: For level 10 SubCounter 11