Escolar Documentos
Profissional Documentos
Cultura Documentos
Contents
1. Overview 2. 2G Performance Monitoring and Analysis
Document Information
Document Version: 1.0 Issue Date: September 8, 2010 Author: Christos Kyriazopoulos Document Owner: Ville Salomaa SOFTWARE RELEASE: GBSS9.0 SCOPE: 2G performance monitoring and analysis CONVENTION: Raw counters are marked in BLUE Formulas are marked in GRAY Parameters are marked in RED MML commands are marked in GREEN
Contents
1. Overview 2. 2G Performance Monitoring and Analysis
Overview
The purpose of this document is to describe the BSS KPI performance monitoring and analysis of problems that bad KPI values indicate. The following analysis contains a list of the most common KPIs used in Huawei networks. These KPIs are monitored constantly. When the value of a KPI goes below the defined threshold, then detailed analysis should be performed in order to identify the reasons of this deterioration. Once the reasons are found, proper solutions will be proposed and implemented. This document focuses more in the analysis of failure causes rather than the KPI monitoring itself. The most common use cases for monitoring and analysis of bad values are presented for 2G BSS.
General Methodology
General Methodology: 1. Define BSS KPI class required (Accessibility, Retainability, Mobility, Resource Usage). 2. Define KPI per service (Voice, Packet Service). 3. Define KPI formulas. 4. Define target or guaranteed KPI values. 5. Assess weekly average PLMN/BSC KPI performance in order to identify KPIs below target. 6. Assess BSC/Area level performance in order to check if bad performance occurs across network or only in specific areas. 7. Analyze bad performing KPIs in cell level in order to identify failure causes. (this point is the focus of this document) 8. Use TopN cell approach to identify the worst performers. Identify top 20 worst cells. 9. Look at failure distribution in network topology (urban, rural, motorway, RNC border, etc.). 10. Propose solution to improve KPI value.
Contents
1. Overview 2. 2G Performance Monitoring and Analysis
4.
5. 6.
Note: for more details on SDCCH capacity optimisation check HUA_2G_Capacity_Optimization_v1.0.pptx document from Multivendor Team in IMS.
For internal use 11 Nokia Siemens Networks
3. CSSR (1)
- KPI formula: BSS Call Setup Success Rate = (([Immediate Assignment Success Rate]*[TCH Assignment Success Rate])*(1-[SDCCH Drop Rate]))*{100} The CSSR combines 3 other KPIs: - Immediate Assignment Success Rate = ([Call Setup Indications (Circuit Service)]/[Channel Requests (Circuit Service)])*{100} - TCH Assignment Success Rate = ([Successful Assignments]/[Assignment Requests])*{100} - SDCCH Drop Rate = ([Call Drops on SDCCH]/[Successful SDCCH Seizures])*{100} Analysis process: 1.Each of the 3 component-KPIs will affect CSSR: - Low Immediate Assignment Success Rate will decrease CSSR - Low TCH Assignment Success Rate will decrease CSSR - High SDCCH Drop Rate will decrease CSSR 2.Examine at which point most of the failures appear by checking thoroughly the 3 component-KPIs. Find out the corresponding failure causes for Immediate Assignment, Assignment and SDCCH Drops.
3. CSSR (2)
3. Low Immediate Assignment Success Rate Basic Immediate Assignment signalling procedure:
Fig.2 Failed Immediate Assignment A: The BSC sends an IMM ASS REJ message due to no available channel B: The BSC sends an IMM ASS REJ message due to channel activation failure C: The BSC sends an IMM ASS REJ message due to channel activation timeout
3. CSSR (3)
If Immediate Assignment failures are due to no channel available (point A in Figure 2), this means that there is SDCCH congestion. Refer to Case 1 of present document for handling. If Immediate Assignment failures are due to channel activation failure or channel activation timeout (points B, C in Figure 2) check hardware/software alarms. 4.Low TCH Assignment Success Rate Basic Assignment signalling procedure:
3. CSSR (4)
Check following counters to identify the reason for Assignment failure: (1) Failures due to mismatch between the state machine of the BSC and the ASS REQ message or due to the abnormality of the ASS REQ message: - A3129I: CELL_ASS_FAIL_INVALID_STATE: This counter provides the number of ASS FAIL messages sent by the BSC to the MSC when the BSC receives an ASS REQ message that is not expected by the internal state machine of the BSC (for example, the state machine is in release status). - A3129J: CELL_ASS_FAIL_INVALID_MSG_CONTENTS: This counter provides the number of ASS FAIL messages sent by the BSC to the MSC when the BSC receives an ASS REQ message but the ASS REQ message fails to be decoded (for example, an error occurs during the decoding of an IE, such as CHANNEL TYPE, CIC, or Layer 3 header information). - A3129E: CELL_ASS_FAIL_NO_CIC: This counter provides the number of ASS FAIL messages sent by the BSC to the MSC when the BSC receives an ASS REQ message that carries an unavailable A interface CIC. - A3129F: CELL_ASS_FAIL_CIC_ALLOC: This counter provides the number of ASS FAIL messages sent by the BSC to the MSC when the BSC receives an ASS REQ message that carries an A interface CIC that is already occupied by another call.
3. CSSR (5)
(2) Failures due to abnormal radio resource allocation: - A312A: CELL_ASS_FAIL_Frst_ASS_NO_CH: This counter provides the number of ASS FAIL messages sent by the BSC to the MSC when the cell does not have available channels and the directed retry procedure fails to be initiated or the directed retry is prohibited by the data configuration in the first air interface assignment procedure. - A312L: CELL_ASS_FAIL_RECONN_SUCC_ASS_NO_CH: This counter provides the number of ASS FAIL messages sent by the BSC to the MSC when the cell does not have available channels and the directed retry procedure fails to be initiated or the directed retry is prohibited by the data configuration in the air interface assignment procedure except for the first air interface assignment procedure. - A312K: CELL_ASS_FAIL_Frst_DR_NO_CH: This counter provides the number of ASS FAIL messages sent by the BSC to the MSC when the cell does not have available channels and the directed retry procedure is successfully initiated but failed due to no available channel in the first air interface assignment procedure. - A312M: CELL_ASS_FAIL_RECONN_SUCC_DR_NO_CH: This counter provides the number of ASS FAIL messages sent by the BSC to the MSC when the BSC attempts to make a directed retry but the directed retry failed because the target cell does not have available channels in the air interface assignment procedure except for the first air interface assignment procedure.
3. CSSR (6)
- A312F: CELL_ASS_FAIL_NO_IDLE_ABIS: This counter provides the number of ASS FAIL messages sent by the BSC to the MSC when the dynamic allocation of Abis resources is enabled on the BSC but the assignment fails due to no available Abis resources. - A3129S: CELL_ASS_FAIL_NO_SPEECH_VER: This counter provides the number of ASS FAIL messages sent by the BSC to the MSC when the assignment fails because the intersection between the speech version set carried in the ASS REQ message from the MSC and the speech version set supported by the current cell of the MS does not have available speech versions.
(3) Failures due to abnormal air interface access: - A3129C: CELL_ASS_FAIL_Frst_ASS_EXP: This counter provides the number of ASS FAIL messages sent by the BSC to the MSC when the timer for the BSC to wait for an ASS CMP message expires after the BSC sends an ASS CMD message to the MS in the first air interface assignment procedure. - A3129P: CELL_ASS_FAIL_RECONN_SUCC_ASS_EXP: This counter provides the number of ASS FAIL messages sent by the BSC to the MSC when the timer for the BSC to wait for an ASS CMP message expires after the BSC sends an ASS CMD message to the MS in the air interface assignment procedure except for the first air interface assignment procedure.
3. CSSR (7)
- A3129O: CELL_ASS_FAIL_Frst_DR_EXP: This counter provides the number of ASS FAIL messages sent by the BSC to the MSC when the cell does not have available channels and the directed retry procedure is successfully initiated but failed due to the expiry of the timer for waiting for an HO CMP message in the first air interface assignment procedure. - A3129Q: CELL_ASS_FAIL_RECONN_SUCC_DR_EXP: This counter provides the number of ASS FAIL messages sent by the BSC to the MSC when the timer for waiting for an ASS CMP message expires after the BSC sends an HO CMD message to the MS in the air interface assignment procedure except for the first air interface assignment procedure. - A3129D: CELL_ASS_FAIL_RECONN_SUCC_ASS_RECONN_SUCC: This counter provides the number of ASS FAIL or RR STATUS messages reported by the MS to the BSC when the MS attempts but fails to access the new channel and then successfully reconnects to the old channel after receiving an ASS CMD message. - A3129R: CELL_ASS_FAIL_RECONN_SUCC_DR_RECONN_SUCC: This counter provides the number of HO FAIL or RR STATUS messages reported by the MS to the BSC when the MS attempts but fails to access the new channel and then successfully reconnects to the old channel after receiving an HO CMD message.
3. CSSR (8)
(4) Failures due to the abnormality of terrestrial resources or the call clearing performed by the MSC. - A3129B: CELL_ASS_FAIL_Frst_APPLY_TRSL_FAIL: This counter provides the number of ASS FAIL messages sent by the BSC to the MSC when the MS drops from the connection to the air interface, or a circuit fails to be obtained for the call, or the obtained circuit is faulty during the circuit connection of the BSC in the first air interface assignment procedure. - A3129N: CELL_ASS_FAIL_RECONN_SUCC_APPLY_TRSL_FAIL: This counter provides the number of ASS FAIL messages sent by the BSC to the MSC when the MS drops from the connection to the air interface, or a circuit fails to be obtained for the call, or the obtained circuit is faulty during the circuit connection of the BSC in the air interface assignment procedure except for the first air interface assignment procedure. - A3129G: CELL_ASS_FAIL_A_INTERF_FAIL: This counter provides the number of times that the BSC locally releases the call when the BSC receives an SS7 link abnormality indication in the assignment procedure. - A3129H: CELL_ASS_FAIL_MSC_CLR_CMD: This counter provides the number of times that the BSC releases the call after receiving a CLEAR CMD message from the MSC in the assignment procedure.
3. CSSR (9)
5. High SDCCH Drop Rate In case high SDCHH Drop Rate causes deterioration of CSSR, refer to Case 2 of present document for handling. 6. Parameters that affect CSSR
- RACHACCLEV: RACH Min. Access Level This parameter affects the coverage area. If this parameter is set to a higher value, the actual coverage area of the network becomes small; if this parameter is set to a lower value, call drops are likely to occur because of invalid access or too weak access signals, thus decreasing the success rate of BSS call setup. - RACHBUSYTHRED: RACH Busy Threshold This parameter affects the coverage area. If this parameter is set to a higher value, the actual coverage area of the network becomes small; if this parameter is set to a lower value, call drops are likely to occur because of invalid access or too weak access signals, thus decreasing the success rate of BSS call setup. - RANERRTHRED: Random Access Error Threshold This parameter affects the coverage area. If this parameter is set to a higher value, the actual coverage area of the network becomes small; if this parameter is set to a lower value, call drops are likely to occur because of invalid access or too weak access signals, thus decreasing the success rate of BSS call setup.
For internal use 22 Nokia Siemens Networks
- CIC No. / Author / Date The values of CICs must be Presentation consistent with that on the MSC side.
3. CSSR (10)
7. Network functions that affect CSSR - Directed retry When TCHs in a cell are insufficient, TCHs in other cells can be assigned through directed retry, thus increasing the BSS CSSR. By default, this function is enabled. - SDCCH dynamic adjustment When SDCCHs are insufficient, this function can be enabled to convert some TCHs into SDCCHs to increase the success rate of immediate assignment, thus increasing the BSS CSSR. By default, this function is enabled. - TCH reassignment When this function is enabled, the BSC initiates a re-assignment procedure after receiving the failure indication of the TCH assignment on the Um interface. This function can be used to increase the success rate of TCH assignment, thus increasing the BSS CSSR. By default, this function is enabled. - Flex Abis This function is implemented in the BSC6000V900R003 and later versions. This function enables dynamic assignment of Abis timeslots to more efficiently utilize the Abis link resources; however, assignment may fail because of congestion on the Abis links. This function may decrease the BSS CSSR.
7.
Note: The counter CH312C:CELL_INTRABSC_OUTCELL_HO_FAIL_EXP is the sum of all the above counters, i.e. the six counters above are sub-items of this counter.
Note: The counter CH332C:CELL_INTERBSC_OUTCELL_HO_FAIL_T8_EXP is the sum of all the above counters, i.e. the six counters above are sub-items of this counter.
(6) The following counter provides the number of failed outgoing external inter-cell handovers when the BSC detects an SS7 link failure on the A interface and releases the call: - H332G:CELL_INTERBSC_OUTCELL_HO_FAIL_MSC_CLR_A_INTF_FAIL
4.
- T3103A: Timer started after the BSC delivers a HANDOVER COMMAND in an intra-BSC inter-cell handover. If the BSC receives a HANDOVER COMPLETE message before this timer expires, the timer stops. If this timer expires, the BSC considers the handover as failed. Recommended value: 10000 ms - T7: Timer is started after the BSC sends the HO RQD to the MSC and waits for the HO CMD command from the MSC in an inter-BSC inter-cell handover procedure. Recommended value: 10000 ms - T8: After sending the HO CMD message to the MS, the BSC starts this timer to wait for the CLEAR CMD message from the MSC in an inter-BSC inter-cell handover procedure. Recommended value: 10000 ms
- S4420A:TRX_MR_NUM_BY_TA_20 - S4421A:TRX_MR_NUM_BY_TA_21 - S4422A:TRX_MR_NUM_BY_TA_22 - S4423A:TRX_MR_NUM_BY_TA_23 - S4424A:TRX_MR_NUM_BY_TA_24 - S4425A:TRX_MR_NUM_BY_TA_25 - S4426A:TRX_MR_NUM_BY_TA_26 - S4427A:TRX_MR_NUM_BY_TA_27 - S4428A:TRX_MR_NUM_BY_TA_28 - S4429A:TRX_MR_NUM_BY_TA_29 - S4430A:TRX_MR_NUM_BY_TA_30_TO_31 - S4432A:TRX_MR_NUM_BY_TA_32_TO_33 - S4434A:TRX_MR_NUM_BY_TA_34_TO_35 - S4436A:TRX_MR_NUM_BY_TA_36_TO_37 - S4438A:TRX_MR_NUM_BY_TA_38_TO_39 - S4440A:TRX_MR_NUM_BY_TA_40_TO_44 - S4445A:TRX_MR_NUM_BY_TA_45_TO_49 - S4450A:TRX_MR_NUM_BY_TA_50_TO_54 - S4455A:TRX_MR_NUM_BY_TA_55_TO_63 - S4463A:TRX_MR_NUM_BY_TA_GT_63
Receive Level Measurement, together with Receive Quality Measurement per TRX, reflects the radio signal coverage and interference of a cell. For example, a high ratio of high level and low quality suggests possible interference; a high ratio of low level and low quality suggests poor coverage.
For internal use 46 Nokia Siemens Networks
where: aaaaa=counter ID, x=receive level rank (0~7), y=receive quality rank (0~7) TCHH Receive Level Measurement per TRX refers to the measurement of the sampled receive level ranks and receive quality ranks in the MRs on the TCHH. TCHH receive level and quality measurements for UL and DL are given by following counters: - S4100C:TRX_HR_UP_LEV_0_RX_QLTY_0 - S4101C:TRX_HR_UP_LEV_0_RX_QLTY_1 - S4102C:TRX_HR_UP_LEV_0_RX_QLTY_2 Saaaaa:TRX_HR_UP_LEV_x_RX_QLTY_y - S4100D:TRX_HR_DOWN_LEV_0_RX_QLTY_0 - S4101D:TRX_HR_DOWN_LEV_0_RX_QLTY_1 - S4102D:TRX_HR_DOWN_LEV_0_RX_QLTY_2 Saaaaa:TRX_FR_UP_LEV_x_RX_QLTY_y
where: aaaaa=counter ID, x=receive level rank (0~7), y=receive quality rank (0~7)
For internal use 47 Nokia Siemens Networks
2. Rxlevel & Quality distributions can be used to identify interference in a cell. Refer to Case 7 of present document for details. 3. TA measurements can be used to identify interference in a cell. Refer to Case 7 of present document for details.
For internal use 49 Nokia Siemens Networks Presentation / Author / Date
6.
7.
8. 9.
MS
BTS Channel Request Immediate Assignment RLC data block(with TLLI) Packet Uplink Ack/Nack(with TLLI) RLC data block(without TLLI) RLC data block(without TLLI) Packet Uplink Ack/Nack(without TLLI) RLC data block(without TLLI)
BSC
MS
BTS Channel Request Immediate Assignment Packet Resource Request(with TLLI) Packet Uplink Assignment(with TLLI) RLC data block RLC data block Packet Uplink Ack/Nack RLC data block
BSC
Analysis process: 1.Identify the possible cause of the TBF establishment failures by checking the following counters: A. UL GPRS TBF establishment failures: - A9003:UP_GPRS_TBF_ESTB_FAIL_NO_CHAN_RES: number of failed uplink GPRS TBF establishments due to no channel available. Indicates congestion on the TCH; refer to Case 4 of present document for handling suggestions. - A9004:UP_GPRS_TBF_ESTB_FAIL_MS_NO_RESP: number of failed uplink GPRS TBF establishments due to no response from MS. Indicates bad RF conditions in the cell. Check cell coverage and interference. - A9037:UP_GPRS_TBF_ESTB_FAIL_SEND_ASSMSG_FAIL: In dedicated mode, the BSS sends the resource assignment command to the MS over the DCCH if both the network and the MS support DTM (Dual Transfer Mode simultaneous support of CS+PS service). If the resource assignment command is not sent successfully and the establishment of the uplink GPRS TBF thus fails, this counter is incremented by one.
For internal use 53 Nokia Siemens Networks
Note: For more details on how to cope with Abis interface congestion refer to HUA_2G_Capacity_Optimization_v1.0.pptx document from Multivendor Team in IMS.
References
HUA_2G_Capacity_Optimization_v1.0, Multivendor Team, IMS: https://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D420911578
THANK YOU