OMC 统计数据常用公式FZMCC Swordup Lin OMC 统计数据常用公式整理 -1- .....................................................2 SDCCH 话务情况............................3 TCH drop calls in intra-cell HO........................................................14 -2- .........................................................................................7 TCH drop call %....................................1 SDCCH 配置.................2........................10 3 现网使用的公式.................................................................................................................................................................. area................................................9 2.............................................................................................................................................................................................11 3........1 站点相关信息.....................................................................2 SDCCH 配置与话务......3 1......................................................................................11 3....................12 3..................9 2.......9 2.................2....2 1 SDCCH drop failure..............4 掉话与拥塞..........................4 1...............................................................................1 TCH 信道配置...3 TCH 配置与话务....................................4..........................................1 TCH drop calls in HO...................................................9 2........3 Illegal establishment cause (Ghost).......14 3..........................................4 TCH drop calls in intra-BSC HO..................7 2............................................................................5 Drop calls in BSC incoming HO................2...............................................2............OMC 统计数据常用公式 FZMCC Swordup Lin 1 目录 1 目录.........................................................7 2......2.................2 TCH drop calls in BSC outgoing HO..........................11 3...............................................................1 SDCCH 掉话数...............................................14 3..........................................9 2..............................................................................................................2 常用公式.............................3........1 相关计算器 Counter 说明.......................................................1 掉话详情......................................................................................................4..................12 3....................2.................................3 1.2............4 1...............2...................................11 3..4 1..2 SDCCH 掉话率..............................................................2 阻塞详情..........................9 2....................................................................................................................................................6 TCH drop calls in HO..........................................................2 TCH 话务情况............................1 相关计算器 Counter 说明.....................................................2...............................................................................................2.......................................................................2.13 3..11 3....................2..................................5 2 TCH drop failure..............................3................ or more commonly when a timer (T3101. One reason for multiple SDCCH seizures can be DL interference. it is possible that there will be multiple reservations of SDCCH for one mobile naturally the mobile can use only one of these and the rest will eventually time out and result in sdcch_abis_fail_call.For instance.OMC 统计数据常用公式 FZMCC Swordup Lin 1 SDCCH drop failure 1.1 相关计算器 Counter 说明 SDCCH_RADIO_FAIL： A coverage problem. SDCCH_RF_OLD_HO : Transactions have ended due to an old channel failure in HO. SDCCH_ABIS_FAIL_OLD : Same as above but when trying to return back to the old channel in HO. Triggered also if the MS user clears the call in the SDCCH phase. • Ghost seizures which accidentally have a valid establishment cause and are detected on SDCCH. SDCCH_LAPD_FAIL: Transactions have ended due to LAPD problems (a call is lost when LAPD goes down). use Clear Code measurement for cause analysis. Augmented when the BSC receives an Establish indication the contents of which are corrupted. a failure in Directed Retry drops the call and triggers this counter in the source cell.for example:MS moves out from timing advance Common in connection with coverage problems. If this occurs in the entire network or BSS areas. the share is normally very low because the situation is -3- . Missing channel activation ack or if no indication of call establishment has been received. default 3 sec) expires while waiting for the Establish indication. increment this counter. • A more rare yet possible reason are failing LUs.3 second peaks with high blocking rate on SDCCH. A high value can be related to IMSI detaches (in S3). • Too short frequency&BSIC reuse distance may cause HO burst from one cell to be interpreted as RACH bursts in another cell causing false SDCCH seizures. SDCCH_A_IF_FAIL_CALL: Transactions have ended due to A interface problems. 2 . If the MS has to send multiple random accesses for a call or location update. TRX/TSL is blocked with cause lapd_fail due to a signalling link fault or a PCM fault. This reason may be suspected if there are short. See #1 for all possible causes. SDCCH_A_IF_FAIL_OLD : Same as above but when trying to return back to the old channel in HO. SDCCH_ABIS_FAIL_CALL: Transactions have ended due to Abis problems. • Multiple SDCCH seizures may cause these failures. The Establish indication is the first message sent from the BTS to the BSC after the MS has successfully accessed the SDCCH. Even if it occurs. SDCCH observation may be used to diagnose the cause on cell level. 1 SDCCH 掉话数 1.OMC 统计数据常用公式 FZMCC Swordup Lin transient.2 SDCCH 掉话率 Tables：p_nbsc_traffic Notes： 1) High SDCCH drop rates usually result from ghost accesses. -4- . A timeslot or TRX is locked by the user via the Top-level User Interface or BSC MML. the share is normally very low because the situation is transient. three of which are undefined as invalid. the share is normally very low because the situation is transient. In GSM ph. A call is lost when TRX/TSL is blocked with cause bts_fail due to FU or CU or BCF fault or BTS or BCF reset. the share is normally very low because the situation is transient.2. SDCCH_NETW_ACT : Transactions have ended due to a change in the radio network configuration (BCCH swap to another TRX) initiated by the BSC.1 there exist altogether eight establishment causes. The cause for the configuration change fails or locally blocked BCCH TRX. A BTS decodes them from environmental or background noise and filters out most of them.2 常用公式 1. SDCCH_BCSU_RESET: Transactions have ended due to BSCU reset (calls are lost when BSCU is reset). 1. However. the share is normally very low because the situation is transient. Even if it occurs. all of them cannot be filtered out and the RACH request is passed on to the BSC for processing and for the allocation of a SDCCH channel. Even if it occurs. Even if it occurs. SDCCH_BTS_FAIL: Transactions have ended due to BTS problems.2. SDCCH_USER_ACT: Transactions have ended due to user actions.The counter ghost_ccch_res (3030) is updated each time a channel required is rejected because of an invalid establishment cause. Even if it occurs. -5- . For the rest. As the amount of call attempts increases.3 Illegal establishment cause (Ghost) Notes： This PI gives you the number of ghost accesses which try to seize SDCCH but are rejected before seizing SDCCH due to an illegal establishment cause.OMC 统计数据常用公式 FZMCC Swordup Lin for example. the influence of ghosts becomes smaller and the drop ratio approaches its real value. 2) The rate of ghosts coming to SDCCH dropped when BTS B9 with improved ghost filtering was taken into use. Because of ghost attempts the SDCCH drop ratio is high with low traffic. 1.2.resulting in that this counter shows only 3/8 of all the ghost accesses the BTS has decoded. a SDCCH is allocated and this will result in sdcch_abis_fail_call failure. OMC 统计数据常用公式 FZMCC Swordup Lin -6- . a BSU reset in MSC makes MSC send a "reset circuit" message.OMC 统计数据常用公式 FZMCC Swordup Lin 2 TCH drop failure 2. we may expect that we start to see ghost seizures incrementing this counter because the signalling tries to use SDCCH instead of TCH. TCH_ABIS_FAIL_CALL: • missing ack of channel activation • missing establishment indication • reception of error indication • corruption of messages • measurement results no longer received from BTS • excessive timing advance • missing HO detection • T3107 (assignment completely missing) expiry • T3109 expiry. the MS user cannot see the situation as a drop call. This failure type is usually the dominating one. For example. If FACCH call setup is used. See #1 for all possible causes that trigger this counter. you can see its share to be high for one BSC. TCH_ABIS_FAIL_OLD: Same as above but when trying to return to the old channel in HO TCH_A_IF_FAIL_CALL: • A clear command from the MSC during the call setup phase before the assignment from MS is complete • Abnormal clear received due to A-interface (reset circuit. If this failure is related to a transcoder.There have been cases where the MSC of another vendor in inter-MSC handovers has caused high values even though the handovers have been successful. -7- .The BTS suffering from this failure can be faulty or their TCH TRX suffers from bad interference (TCH assignment fails). Can be updated when GSM timer T8 expires in the source BSC during an external handover. TCH_TR_FAIL: • Transcoder failure during a call attempt .1 相关计算器 Counter 说明 TCH_RADIO_FAIL ：• Radio link timeout • Release indication from MS • MS moves out from timing advance • TCH assignment failure where an Establish Indication has been received but Assignment Complete has not been received . TCH_A_IF_FAIL_OLD: Same as above but when trying to return to the old channel in HO.This counter is updated only when BTS sends a "connection failure" with cause "remote trascoder failure" and the call is released due to this. TCH_RF_OLD_HO: Same as above but when trying to return to the old channel in HO.This counter is typical in connection with coverage problems. See #1 for all possible causes that trigger this counter. SCCP clear). As in this case the drop happens in the release phase. -8- . you may find it helpful to check the pattern over a longer period of time. To analyse the case in question.In S6 the portion of this failure has decreased due to improvements in transcoders. Even if it occurs. TCH_ACT_FAIL_CALL： Channel activation nack received. the share is very small because only ongoing calls are dropped when reconfiguration is executed. TCH_BCSU_RESET: TRX is blocked by BCSU reset. *_OLD counters are related to the handover situation when returning to the old channel fails causing a call to drop. As there are limitations on how to set the observations. Thus. Even if it occurs. TCH_USER_ACT: Busy TSL or TRX blocked by MML command (blocked by user). the share is very small because only ongoing calls are dropped when the blocking command is given. BTS reset. Even if it occurs. Even if occurs. the share is very small because only ongoing calls are dropped when a BTS fails. CU fault. the share is very small because only ongoing calls are dropped when BCSU resets. you can also use the Clear Code measurement. BCF fault). these counters reflect the amount of call drops in handovers. TCH_TR_FAIL_OLD: Same as above but when trying to return to the old channel in HO. If the problem is not cell specific but related to the entire network or BSS areas. the share is very small because only ongoing calls are dropped when the LAPD fails.OMC 统计数据常用公式 FZMCC Swordup Lin Another possibility is that the problem lies in a BTS. TCH_LAPD_FAIL: TRX is blocked due to a LAPD failure (signalling link failure or PCM failure). Also interruptions of the transmission may cause this failure (alarms may be filtered out in a BSC or OMC to reduce the number of alarms due to disturbance). the analysis is more time-consuming. CU and FU fault. TCH_NETW_ACT: TRX is blocked by a fault leading to reconfiguration (blocked by the system). TCH_BTS_FAIL: TRX is blocked by a BTS failure. TCH observations may be used. (FU fault. BCF reset. The problem especially with failure classes Abis and Aif is that they are triggered by many different causes. Even if it occurs. In analysing the problem. 1 TCH drop calls in HO 2.2.2.2.3 TCH drop calls in intra-cell HO sum(cell_drop_calls) Counters from table(s): p_nbsc_ho 2.6 TCH drop calls in HO -9- .2.2.OMC 统计数据常用公式 FZMCC Swordup Lin 2.4 TCH drop calls in intra-BSC HO 2.2 TCH drop calls in BSC outgoing HO 2.2.5 Drop calls in BSC incoming HO 2. OMC 统计数据常用公式 FZMCC Swordup Lin 2. area .7 TCH drop call %.10 - .2. 1 SDCCH 配置 1:SDCCH 可用信道数： decode(sum(RES_AV_DENOM3).sum(AVE_SDCCH_SUB )/sum(RES_AV_DENOM3)+sum(AVE_NON_AVAIL_SDCCH)) Table: P_nbsc_res_avail 3.sum(AVE_NON_AVAIL_SDCCH).2.1 站点相关信息 FLDSNAME ：基站中文名 FLDICELLID ：扇区 CI 号 FLDSREGION ：所属地区 FLDSBSCNAME ：该基站所属 BSC FLDILAC ：LAC FLDIINT_ID ：BTS 的 internal ID，全网唯一。用于关联其他表。 FLDIBTS_ID ： BTS Number FLDIBCCH ： BCCH FLDITRXNUM ：TRX 数 FLDIBSIC_NCC：NCC FLDIBSIC_BCC ：BCC Table： all_BTS ( in databace：fjnmc) Objects.0.0.bcf_type 站点类型 Table：Objects (in databace:fzomc) 3.2.11 - .OMC 统计数据常用公式 FZMCC Swordup Lin 3 现网使用的公式 3.sum(AVE_SDCCH_SUB)/sum(RES_AV_DE NOM3)) 2: SDCCH 信道总数： decode(sum(RES_AV_DENOM3).0.2 SDCCH 话务情况 1：SDCCH 试呼数： sum(SDCCH_SEIZ_ATT) .2 SDCCH 配置与话务 3. 0.3 TCH 配置与话务 3.sum(SDCCH_BUSY_ATT)/sum(SDCCH _SEIZ_ATT)).0.sum(AVE_NON_AVAIL_TCH).sum(AVE_BUSY_SDCCH)/sum(R ES_AV_DENOM15)).0.12 - . (sum(AVE_AVAIL_FULL_TCH)/sum(RES_AV_DENOM2)+sum(AVE_NON_AVAIL _TCH))) .3.4) Table: P_nbsc_traffic 4：SDCCH 掉话率 sum(SDCCH_RADIO_FAIL+SDCCH_RF_OLD_HO+SDCCH_ABIS_FAIL_OLD+SDCC H_A_IF_FAIL_CALL+SDCCH_A_IF_FAIL_OLD+SDCCH_LAPD_FAIL+SDCCH_BTS_FA IL+SDCCH_USER_ACT+SDCCH_BCSU_RESET+SDCCH_NETW_ACT)/sum(SDCCH_ SEIZ_ATT) Table: P_nbsc_traffic 4：SDCCH 话务量 round(decode(sum(RES_AV_DENOM15).0.OMC 统计数据常用公式 FZMCC Swordup Lin 2：SDCCH 掉话数： sum(SDCCH_RADIO_FAIL+SDCCH_RF_OLD_HO+SDCCH_ABIS_FAIL_OLD+SDC CH_A_IF_FAIL_CALL+SDCCH_A_IF_FAIL_OLD+SDCCH_LAPD_FAIL+SDCCH_BTS_F AIL+SDCCH_USER_ACT+SDCCH_BCSU_RESET+SDCCH_NETW_ACT) Table: P_nbsc_res_avail 3: SDCCH 阻塞数： sum(SDCCH_BUSY_ATT) Table: P_nbsc_traffic 3: SDCCH 阻塞率： round(decode(sum(SDCCH_SEIZ_ATT).0.1 TCH 信道配置 1: TCH 总信道数： decode(SUM(RES_AV_DENOM2).2) Table: P_nbsc_traffic 3. Table：p_nbsc_traffic 4: TCH 占用总数 sum( tch_norm_seiz+tch_ho_seiz) Table：p_nbsc_traffic . Table：p_nbsc_traffic 2: TCH 试呼占用数 sum(tch_norm_seiz) Number of successful TCH requests for a normal assignment UPDATED: When the Radio Resource Manager allocates a TCH as a response to a TCH request in a call attempt.flditrxNum 3.13 - .3.2 TCH 话务情况 1: TCH 试呼数 sum(tch_call_req) 不包含 DR 的试呼数 Number of TCH requests for normal assignment (successful + unsuccessful) UPDATED: When the Radio Resource Manager receives a TCH request in a call attempt.OMC 统计数据常用公式 FZMCC Swordup Lin 2: 可用 TCH 信道数 sum(AVE_AVAIL_FULL_TCH/RES_AV_DENOM2) 3: TRX 数 All_BTS. Table：p_nbsc_traffic 3: TCH 切换占用数 Sum(TCH_HO_SEIZ) Number of successful TCH requests for handover purposes UPDATED: When the Radio Resource Manager allocates a TCH as a response to a TCH request in a handover attempt. TCH_TR_FAIL_OLD+B.4. 2: TCH 阻塞率 100*decode(sum(TCH_CALL_REQ).14 - .sum(TCH_CALL_REQ-TCH_NORM_SEIZ-BSC_O_S DCCH_TCH-CELL_SDCCH_TCH-MSC_O_SDCCH_TCH)/sum(TCH_CALL_REQ)) .TCH_A BIS_FAIL_OLD+B.TCH_BTS_FAIL) Table：p_nbsc_traffic 2: RF 掉话 sum(tch_radio_fail+tch_rf_old_ho) 3:RFHO 掉话 sum(tch_rf_old_ho) 4: TR 掉话 sum(tch_tr_fail+tch_tr_fail_old) 5: ABIS 掉话 sum(tch_abis_fail_call+tch_abis_fail_old) 6: AIF 掉话 sum(tch_a_if_fail_call+tch_a_if_fail_old) 7: LAPD 掉话 sum(tch_lapd_fail) 3.0.1 掉话详情 1: TCH 掉话数 sum(B.2 阻塞详情 1:TCH 阻塞数 sum(TCH_CALL_REQ-TCH_NORM_SEIZ-BSC_O_SDCCH_TCH-CELL_SDCCH_TCHMSC_O_SDCCH_TCH).4 掉话与拥塞 3.4.TCH_A_IF_FAIL_OLD+B.TCH_ABIS_FAIL_CALL+B.TCH_LAPD_FAIL+B.TCH_RADIO_FAIL+B.TCH_A_IF_FAIL_CALL+B.OMC 统计数据常用公式 FZMCC Swordup Lin 3.TCH_RF_OLD_HO+B.TCH_TR_FAIL+ B.0. 0.0.15 - .sum(AVE_BUSY_T CH/RES_AV_DENOM14)/ sum(AVE_AVAIL_FULL_TCH/RES_AV_DENOM2)).2) .OMC 统计数据常用公式 FZMCC Swordup Lin 3: 话务量 sum(round(AVE_BUSY_TCH/RES_AV_DENOM14.2)) 4: 每线 ERL round(decode(sum(AVE_AVAIL_FULL_TCH/RES_AV_DENOM2).