Академический Документы
Профессиональный Документы
Культура Документы
7745 - CHANNEL FAILURE RATE ABOVE DEFINED THRESHOLD Channel Release procedure
Whenever a channel is released with a release cause other than a normal one, the counter of channel failures for the released channel is incremented. After a certain observation time and a certain threshold it will reported in the 7745 alarm. It give an indication that theres a failure that need to be addressed, but overall KPI need to be used as a first priority.
3 Nokia Siemens Networks. All rights reserved.
SDCCH Failure 03 SDCCH radio failure 04 Source SDCCH radio failure in HO 05 Target SDCCH radio failure in HO 0A Channel state conflict between RRMPRB and ABIPRB 0B Channel type conflict between RRMPRB and ABIPRB 23 SDCCH failure due to a LAPD failure 24 SDCCH failure due to a BTS failure 25 SDCCH failure due to user actions 26 SDCCH failure due to a BCSU reset 27 SDCCH failure due to radio network reconfiguration actions 48 SDCCH activation failure during call set-up 4A Target SDCCH activation failure in HO 4B SDCCH failure due to an Abis interface failure in call set-up 4C Source SDCCH failure due to an Abis interface failure in HO 4D Target SDCCH failure due to an Abis interface failure in HO 4E SDCCH failure due to an A interface failure in call set-up 4F Source SDCCH failure due to an A interface failure in HO 50 Target SDCCH failure due to an A interface failure in HO
Tools or verification that have been performed so far by NSN before/during site visit
Basic SW for Monitoring NE
MML, BTS Manager
KPI Browser
Cell Doctor (report 211 Network Doctor) OSS Cell KPI (report 204 Network Doctor) OSS
Action on site :
1.
7745, 7743 at one TRX only - Check SMA cable at Tx connector to WCXA of the TRX, make sure properly connected - Replace TRX, BB2F and SMA cables if needed 7745, 7743 at two TRX - Try to switch BCCH, if still appear potential have a partial cross feeder - Replace TRX, BB2F WCXA, or DVXA if needed - Check alarms of other sector to ensure analysis 7745, 7743 at all TRXs under same cell - Possibilities error : full partial cross feeder, bad feeder quality and its connection, interference, broken DVXA
2.
3.
10
Sample ND 196
Performance Analysis: IF: band q5 value is under 95% THEN: we suspect that the TRX have bad quality uplink or Downlink ( in this case downlink issue)
11
Sample ND 195
This report shows for each TRX: Ave MS pwr attn /lb_11 Average MS power attenuation (dB) Ave BS pwr attn /lb_12 Average BS power attenuation (dB) Ave UL str /lb_9 Average UL signal strength Ave DL str /lb_10 Average DL signal strength . The signal (UL, DL) strength is given as value 0..63 (GSM 5.08) . 0 =less than -110dBm, 1= -110 to -109 dBm, 3= -109 to 108dBm . ... 62 = -49 to -48, 63=greater than -48 SAMPLE ABOVE : For Down link TX 1 and TX 2 have big differences , also for TX5 and TX6 for sec 2 For Uplink RX main having 3db diff in sec 1, for sec 2 have 9 db diff
12 Nokia Siemens Networks. All rights reserved.
Base on BTS installation standard that : Uplink and Downlink between TRX in one sector is maks 3db
13
14
15
MancagarMD3 to CiropohMG2 and cisarunimg having 100% fail MancagarMD3 to mancagar MG3 having 85 of 2144 sample call Fail This report showing incoming and outgoing handover
16 Nokia Siemens Networks. All rights reserved.
1. 2. 3.
7745 will keep occur for this condition : No have neighbors cell ( island or remote standalone) Landscape contour ( hill and valley) Obstacle
17
Summary
1. Alarm 7745 occur due to Abnormal release Channel - Mostly in TCH 53,56,59 because of Handover, Call Setup Issue - SDCCH 4B because of antenna and feeder installation 2. Module M6HA should be part of BTS High Capacity 3. Correction related alarm 7745 software CX5 CD4 (replace CX4.1 CD4) 4. Many things that can lead to alarm 7745, it can be categorized as below : Transmission issue, Power Related issue Environment Related, Air Conditioning, Temperature BTS HW problem related, Cooling Fan, Module faulty BTS Antenna Line Coverage Issue Configuration Mismatch between BSC and BTS/MMI Some existing problem in the old SW Other maintenance activity in the BSC level
18
Additional :
RFI Site Procedure Objective: 1. To have better site integration verification procedure 2. To make sure that all functionality of the integration site already in place and being verified 3. To avoid unnecessary mistake on integration such as cross feeder (partial and full), Loose feeder and others functionalities.
19
20
THINGS TO REMEMBER: ND 195: Average /sector range is 3-5 Number of sample preferably >1000 ND 196: Focus result at q5, q6 and q7 UL and DL percentage should be 95 ND 232: Range (km) Area (rural or urban) Number of report (samples) ND 153: To fail = 0
END