Sei sulla pagina 1di 9

Group Cell

Technology GSM

Impact Call setup fail 2G

KPI CSSR_2G

Cell

GSM

GPRS

GPRS_R_Dec

WCEL

UMTS

Call setup fail 3G

CSSR_3G

Cell

GSM

Neighbour Missing

G_UNDEF_ADCE

Cell Cell Cell

GSM GSM GSM

Drop 2G Call setup fail 2G Call setup fail 2G

UL_interf_2G Unbalanced_TRX_2G PoorQual_at_HighLevels

Cell

GSM

Drop 2G

PoorQual_at_HighLevels

Cell

GSM

HOSR 2G

PoorQual_at_HighLevels

BSC Cell

GSM GSM

Drop 2G Drop 2G

TranscFail DCR_2G

WCEL

UMTS

Drop 3G

DCR_3G

RNC

UMTS

Drop Call Rate

IncFails_RAB_ACT_FAIL_ CS_VOICE_BTS

WCEL RNC

UMTS UMTS

Voice & data(R99 & 3G_WCEL_WSP_CONGE HSPA) KPI's STION Packet call Drop 3G_PS_R99_DCR

RNC

UMTS

HSDPA drop call

3G_PS_HSDPA_DCR

RNC

UMTS

HSUPA Drop call

3G_PS_HSUPA_DCR

RNC

UMTS

Drop 3G

INC_CS_CONV_RAB_DC R_RNC INC_CS_STREA_RAB_D CR_RNC

RNC

UMTS

Drop 3G

RNC

UMTS

Drop 3G

INC_PS_BACKG_RAB_D CR_RNC

RNC

UMTS

Drop 3G

INC_PS_CONV_RAB_DC R_RNC

RNC

UMTS

Drop 3G

INC_PS_INTER_RAB_DC R_RNC

RNC

UMTS

Drop 3G

INC_PS_STREA_RAB_DC R_RNC

Cell

GSM

Drop 2G

TCH Drop

CELL

GSM

Drop & Call Setup Fail 2G Call Setup Fail 3G

DCR_2G & CSSR_2G

RNC

WCDMA

RRC_CONN_STP_FAIL_F ROZBS SD Blocking

Cell

GSM

Call Setup fail 2G

Cell

GSM

Call Setup fail 2G

SD Drop

Cell

GSM

Call Setup Fail 2G

TCH Assignment

Cell

GSM

HO Performance 2G

HOSR(Handover success rate)

Cell

GSM

Hardware failure

G_TrxLoopTest

GSM

Call Setup Fail 2G HO success rate 2G Drop Call Rate 2G

SQ_DL SQ_DL SQ_DL

CELL
GSM

CELL
GSM

CELL Cell WCDMA Packet session success rate. PSSR

Long description ( Trigger point when these KPIs are checked) Triggers if a cell has > 50 failures and CSSR is below 95% during any three hours during the past 24h. Triggers if a GSM cell has more than 500 TBFs daily and GPRS_R (current day) < 0.7*GPRS_R compared to any days during the past seven days. Triggers if a cell has > 3 failures and CSSR is below 98% during any three hours during the past 24h. All GSM mobiles measure the GSM frequencies defined for the adjacency BCCH frequencies. Mobiles report all measurements including the BSIC to the BSC. If a measurement report includes a BCCH BSIC combination which does not belong to any defined adjacent cell, the undefined adjacency statistics are updated. If a certain BCCH BSIC is measured several times, it is very likely that there is a cell (with this BCCH BSIC combination) which is not defined as a neighbour although it should. Triggers if a cell has > 0 TCH drops and Idle TCH UL interference measurement above Band1 > 10% during one or more hours during the past 24h. Triggers if a TRX ABS(UL_Qual - DL_Qual) > 0.1 during the past two days and if there are more than 300 measurment samples on the TRX. Triggers if a TRX has < 95% good quality on more than 2 level ranges above -95dBm UL or DL during the past two days and if there are more than 300 measurement samples on the TRX. Triggers if a TRX has < 95% good quality on more than 2 level ranges above -95dBm UL or DL during the past two days and if there are more than 300 measurement samples on the TRX. Triggers if a TRX has < 95% good quality on more than 2 level ranges above -95dBm UL or DL during the past two days and if there are more than 300 measurement samples on the TRX. If a BSC has more than 1.5% share of transcoder failures during the past two (both) days. Triggeres if a 2G cell weekly DCR is 50% higher during all three previous weeks compared to the same weeks during the previous year Triggeres if a 3G cell weekly DCR is 50% higher during all three previous weeks compared to the same weeks during the previous year

Triggeres if a network element has increased failure rate. Failure rate is calculated by dividing the failure counter with the reference counter RAB_ACC_COMP_CS_VOICE. Alarm is triggered if the yesterday failure rate was 45% higher compared to the average of the past three days or any period of three days within the past eleven days and the number of failures is over 100 and failure rate is over 0.02%. Triggeres if a 3G WCEL has over 2% WSP blocking during one hour >= 4 days during the past 28 days. Triggeres if a network element has increased 3G_PS_R99_DCR. Alarm is triggered if the yesterday 3G_PS_R99_DCR was 45% higher compared to the average of the past three days or any period of three days within the past eleven days and the number of failures is over 100 and 3G_PS_R99_DCR is over 0.02%.

Triggeres if a network element has increased 3G_PS_HSDPA_DCR. Alarm is triggered if the yesterday 3G_PS_HSDPA_DCR was 45% higher compared to the average of the past three days or any period of three days within the past eleven days and the number of failures is over 100 and 3G_PS_HSDPA_DCR is over 0.02%. Triggeres if a network element has increased 3G_PS_HSUPA_DCR. Alarm is triggered if the yesterday 3G_PS_HSUPA_DCR was 45% higher compared to the average of the past three days or any period of three days within the past eleven days and the number of failures is over 100 and 3G_PS_HSUPA_DCR is over 0.02%.

Triggeres if RAB DCR trend changes on RNC level or if RAB DCR is higher than 0.5% with more than 20 drops. Triggeres if RAB DCR trend changes on RNC level or if RAB DCR is higher than 0.5% with more than 20 drops.

Triggeres if RAB DCR trend changes on RNC level or if RAB DCR is higher than 0.5% with more than 20 drops.

Triggeres if RAB DCR trend changes on RNC level or if RAB DCR is higher than 0.5% with more than 20 drops.

Triggeres if RAB DCR trend changes on RNC level or if RAB DCR is higher than 0.5% with more than 20 drops.

Triggeres if RAB DCR trend changes on RNC level or if RAB DCR is higher than 0.5% with more than 20 drops.

High TCH Drop due to: Wrong Parameter Planning. BAD HOSR. Hardware Fault. High TR Fail. Overshoot. Due to Low Coverage. Triggers BCF OPERATION DEGRADED due to Power unit temperature is dangerously high.Alarm is activated when the PWSx internal temperature exceeds +85C. RRC Setup Failure due to Frozen BTS,triggers when admission control blocks RL establishment to ensure the setup of emergency calls CSSR impacted if blocking occurs,reasons for SD Blocking: LAC boundary. HW Prob.

Reasons of SD Drop: MAIO mismatch. Bad Coverage. High TR Fail. Overshooting. Abis Drop. High Path Loss. Wrong Parameter Planning. Due to ICM Band(CDMA) High LAPD Utilization Heavy blocking and DR feature being used extensively

Reasons for TCH Assignment failure: Hardware Fault(TRXs,Combiner,Duplexer,Cables) VSWR High Path Loss. Faulty TMA. High TCH Blocking. Loose connections.

Reasons for HOSR: Improper Neighbor planning. CO-BCCH-BSIC issues in Neigh. Parameter Check. HSN clash. SL value. LAC boundary. DAC value mismatch. Syn mismatch. Overshoot. HW Issues. Low Coverage

Cells where TRX loop test failed recently.Normally loop test performed bacause of degradation in downlink quality in TRX or interfarence in TRX.

Triggers when Downlink Quality is impacted. Triggers when Downlink Quality is impacted. Triggers when Downlink Quality is impacted.

Degradation in packet call session success rate.PS_SSR impacted due to degradation in performance for both HSPA & R99 users.

Optimization Suggestion Possible causes are for example: "faulty TRX", "single user with faulty mobile", "faulty timeslot on TRX", "UL or DL interference". A site restart may help especially with cells with active combiners (combiner filter oscillators may drift over time). Config errors may limit GPRS performance. Check GPRS default territory parameters. Site restart may help as well. Other possible causes: Faulty TRX / interference => check if voice traffic has also suffered, Congestion => cell may need an upgrade. First Wcel need to be checked for Congestion or blocking in Radio interface.CE utilization should be checked from reports. The transmission objects COCOs recreated. Normally if a cell has poor CSSR for three hours the problem is not related to SW upgrades or maintenance. Add a new neighbour to the GSM cell. The neighbour must have the same BCCH BSIC combination as the undefined adjacent cell measurement and the cell should be nearby the cell where the alarm was triggered.

High UL interference may be caused by too tight frequency planning, repeaters, faulty HW or external interferers. TRX unbalance may be caused by: repeaters, missing MHAs, diversity turned off, other HW fault (MHA, TRX, combiner), DL interference, attenuation of Tx power, etc. Normally this shows detects faulty HW. The problem is usually a broken TRX but it could also be a drifting oscillator in RTC combiner, faulty MHA, or faulty repeater connected to the cell. Normally this shows detects faulty HW. The problem is usually a broken TRX but it could also be a drifting oscillator in RTC combiner, faulty MHA, or faulty repeater connected to the cell. Normally this shows detects faulty HW. The problem is usually a broken TRX but it could also be a drifting oscillator in RTC combiner, faulty MHA, or faulty repeater connected to the cell. Need to be checked with operations team and replace a faulty transcoder. Sudden DCR increase for a 2G cell is often due to HW fault, e.g. faulty TRX, combiner (if active), or timeslot. Other common reasons: interference UL/DL, changed HO location, database consistency problems, etc.". Sudden DCR increase is often due to HW fault => restart the site. Other reasons: "Changed traffic profile" and therefore missing 2G neighbours, too late ISHO HO => increase ISHO thresholds, "missing 3G adjacency" => Check ADJ Master for autodefined adjacencies, "incorrect database configuration (ADJS objects have wrong parameters)". Find out which sub elements caused the increase (e.g. cells under a RNC or BSC).

Analyse the WCEL to see if the blocking is caused by normal traffic and not by an extraordinary event. BTS FAIL counters should be analysed. Raise WSP upgrade. Identify call drop root cause failure distribution and main failure contributor (radio, Iu, BTS, Iur, MS, RNC) Check if cells are at RNC border (check Iur capacity and SRNC relocation problem) Detect badly performing neighbours using HO success rate per adjacency counters (M1013) High incoming HO failure rate in all adjs check sync alarms Assessing neighbor list plan and visualization check with map Evaluate HO control parameters and trigger threshold Main reason for HSDPA DCR due to Rejected HS-DSCH return channel due to lack of radio power resource Check M1002C521 or M1002C522 or M1000C144 only when HSDPA static allocation Check Cell resource PrxTotal, PtxTotal Check parameter setting for uplink throughput based and interference based admission control There are several reasons for HSUPA release: E-DCH Rel due to RL Failures E-DCH Rel due to Other Failures E-DCH Rel due to HS-DSCH serving cell change. These can be assesed by checking Coverage, Cell update by UE,RLC protocol reset

Check cells on the RNC to find out if all cells on the RNC are impacted. If yes, then the RNC need to be checked for interfaces or ICSU logs. If only one or few cells are impacted, then those cells must be checked thoroughly. This problem could also be related to just one customer. Check cells on the RNC to find out if all cells on the RNC are impacted. If yes, then the RNC need to be checked for interfaces or ICSU logs.Some times mere a restart might help. If only one or few cells are impacted, then those cells must be restarted. This problem could also be related to just one customer. Check cells on the RNC to find out if all cells on the RNC are impacted. If yes, then the RNC might need a restart or problem can be captured through ICSU Log analysis. If only one or few cells are impacted, then those cells must beChecked. This problem could also be related to just one customer. Check cells on the RNC to find out if all cells on the RNC are impacted. If yes, then the RNC might need a restart or problem can be captured through ICSU Log analysis. If only one or few cells are impacted, then those cells must beChecked. This problem could also be related to just one customer. Check cells on the RNC to find out if all cells on the RNC are impacted. If yes, then the RNC might need a restart or problem can be captured through ICSU Log analysis. If only one or few cells are impacted, then those cells must beChecked. This problem could also be related to just one customer. Check cells on the RNC to find out if all cells on the RNC are impacted. If yes, then the RNC might need a restart or problem can be captured through ICSU Log analysis. If only one or few cells are impacted, then those cells must beChecked. This problem could also be related to just one customer. Check the BCCH Plan (C/I or C/A). Co-BSIC & Co BCCH. Check the Timer T 100(should be 20 ms) or Reason was obserevd due to HOSR. Optimize neighbour list. After raised complaint changed faulty power unit & performance is improved.

Issue occurred due to congestion.After addition of system module performance got improved.

Check the No. of SDCCH channel Available, if less then increase SD channel taking care that there is no TCH Blocking. Check LAC boundary, If location update is more then change the LAC of that site and set C2 and HYS. Use of Dynamic SDCCH (It is a BSC parameter and will be applied on whole BTS). Hardware check / shift SD to new time slot Some times BMA and HYS parameters are useful to remove SD Blocking. Hardware Fault: Check Alarms. TRX condition. Check Path Imbalance. VSWR of the Cell. Connector Connection. Some times you will find issues on BCCH TRX.In this case BCCH shift from one to other TRX will reduce SD drop. High LAPD Utilization: Check LAPD util report from OSS, and define 32 kbps signaling instead of 16kbps Overshooting: LAC Planning. If a cell is picking call from long distance, Check the sample log according to TA. Cell orientation need to be defined according to clutter. Mount position Effective Tilt.

Solutions: Clear VSWR IF TRXs are faulty lock them and try to replace them soon to avoid blocking Path Imbalance clear. Connection from BTS to Antenna Connector connection Check TMA. Check Duplexer,Combiner,TRXs connections,Multicuppler etc. Check BOIA card. Check BB2F Card. Arrange Drive Test: The best way to find the real issues for HO fail make DT and check layer 3 msg gor HO fail.By DT it is very easy to find the fail between cells. Neighbor Tuning: Try to retune neighbors Avoid CO-BCCH-BSIC neighbors. Avoid extra neighs. Delete long distance neighs. Check neighs are defined form both ends. If there are high fail delete and recreate neighs. Overshoot: When neighs are far away then chances of HO fail increases. In this case ping-pong HI takes place by which fail takes place. So it the inter distance is high its batter to del that kind of neigh. LAC BoundaryCheck LAC boundry. High fail takes place there will be Inter BSC cells. High fail takes place there will be Inter MSC cells. Define proper LAC in neigh cells. Those TRXs where TRX loop test fails should be analysed either by looking at other cell alarms or investigating performance to make sure the TRX is not causing performance degradation (sometimes a TRX loop test may fail even when the TRX is fine). This alarm can be used together with other alarms to verify a HW problem. Check VSWR,MHA Performance & Site commissioning. Feeder loss -2.3 corrected to -99.0. Site OK. Check VSWR,MHA Performance & Site commissioning. Feeder loss -2.3 corrected to -99.0. Site OK. Check VSWR,MHA Performance & Site commissioning. Feeder loss -2.3 corrected to -99.0. Site OK.

Check HSPA is activated or not.Reset all HSPA Related parameter & perform hard reset of problematic cell.