Beruflich Dokumente
Kultur Dokumente
Document Product
Wireless
Code Name
Intended Wireless BSS Engineer Product
User (GSM/CDMA/WCDMA) Version
Wireless Network
Complied Document
Integration Team, V1.0
by Version
Pakistan
Shahzeb Rauf
Prepared by Date 2012-09-13
S00737002
Reviewed by Date
Reviewed by Date
Approved by Date
In order to improve the Expansion and Rollout quality and to provide an additional support to BSS
Exp & RO teams, this document has been formulated. Document contains overall guidelines from
Management & RF team. Such Issues shouldn’t come under Expansion BSS team and
Who will provide this information Who will be responsible Issue exist (Y/N)
RF Team PMO Team
Who will provide this information Who will be responsible Issue exist (Y/N)
BSS Exp/RO Team BSS Exp/RO Team
should be audited
Who will provide this information Who will be responsible Issue exist (Y/N)
RF Exp/RO Team RF Exp/RO Team
4. Please verify if any BSS hardware alarm exist. Please verify this by analyzing 1 day
event logs of at least 1 day. If yes, please correct it. Zero alarms should be present at
site. Please follow operation & maintenance guide to resolve the hardware alarms
Who will provide this information Who will be responsible Issue exist (Y/N)
BSS Exp/RO Team BSS Exp/RO Team
5. Please verify if any Transmission alarms exist. Please verify this by analyzing 1 day
event logs of at least 1 day. If yes, please correct it. There should not be any
Who will provide this information Who will be responsible Issue exist (Y/N)
BSS Exp/RO Team BSS Exp/RO Team
6. Please verify if any Power related issues exist. Please verify this by analyzing 1 day
event logs of at least 1 day. If yes, please correct it. There should not be any site level
Who will provide this information Who will be responsible Issue exist (Y/N)
BSS Exp/RO Team BSS Exp/RO Team
7. Complete report from RF team is required with all KPI analysis. Also feedback from
Who will provide this information Who will be responsible Issue exist (Y/N)
RF Exp/RO Team RF Exp/RO Team
performance of both.
a) If problem shifts with the DTRU/RRU, then problem is with DTRU/RRU &
replace DDTRU/RRU.
a) If problem shifts with the RF cables, then problem is with cables & replace RF
cables
performance of both.
a) If problem shifts with the DDPU, then problem is with DDPU & replace DDPU.
a) If problem shifts with the CPRI cable, then problem is with CPRI cable.
VSWR and Distance to Fault and take snapshots for the record
If VSWR value is high, please correct the fault by following below step
vi) Verify RF Jumper cables from top of DDPU till Antenna Port for any
damage
If found damaged, please replace the RF jumper cables otherwise continue the
troubleshooting below
vii) Verify each and every RF cable connection. All RF cable connectors
till Feeder cable connection with healthy cable and then monitor
a) If problem shifts with the RF Cable Jumper, then problem is with cable. So
below
ix) SWAP any Combiner/splitter/surge Arrestor installed in RF path with
replace it
c) Antenna Height
d) Antenna Orientation
xii) Check Transmit Power on BTS cabinet top, between RF cable jumpers &
b) If power is reduced between RF cable jumpers & feeder cable, then verify
troubleshooting
NOTE
Missing any single step from these troubleshooting will make all steps null &
Void and all activity need to be re-performed
Please record each activity performed and take snapshots and OMCR logs for
each activity
After each step, please get the feedback from the RF team to confirm the KPI
performance if issue is resolved
After all these activities if no issue is found, then complete hardware has been
verified and issue need to be raised with RF & BSS HQ team while taking GTAC
Team support
After ruling out the hardware Issues, BSS team needs to discuss following points with RF
1. Drive test in the problematic area should be performed to identify some particular
patch where there exist some weak coverage points which is degrading the KPIs
Coverage holes should be identified during the drive test
RX Qual, Rx Level, SQI should be verified and conflicting frequencies & Interference
2. For Handover related issue, Neighbor stats should be verified and shared. It is
possible to have low HSR for 1800 TRX possibly due to low transmit power of 1800 as
compared to 900 TRX while 1800 handovers are failing for some particular cell.
3. Further Drive test as suggested in step-1, could also verify any handover problems or
overshooting sites
Interference, TA)
5. It should be verified if Intra Cell, Inter Cell, Intra BSS, Inter BSS handovers are getting
6. Tilt, HBA and Orientation should be verified from Audit Reports as per plan
Parameter tuning should be discussed and performed on trial basis to improve the
KPI performance.
2019-06-26 Huawei Proprietary - Restricted Distribution Page7, Total9
Troubleshooting Guide for BSS Field Engineers INTERNAL
possibility where previously handovers were being done to some particular cell,
where after congestion on that cell, handover to that cell will not be completed and
call on source cell will either be dropped or in try to handover to another cell (with
10. Outages in neighbor cells should be verified if it related to reported cell degradation.
If outage/fluctuation time matches with KPI degradation, then issue is most probably
11. Interference should be verified on Hourly trend if it is degrading the KPI. External
12. TA for all TRX need to be checked. Incase some TRX TA is much low can indicate it is
should be compared
Such issues can affect HSR, TCH ASR and DCR etc
1. Drive test in the problematic area should be performed to identify some particular
patch where there exist some weak coverage points which is degrading the KPIs
Coverage holes should be identified during the drive test
RX Qual, Rx Level, SQI should be verified and conflicting frequencies & Interference
2. Moreover, Pre-Post SD/TCH traffic KPI should be compared to see any change in total
request types (e.g. Voice Call, SMS, LU, Emergency calls etc). Please note down any
particular type of request increase which can create congestion on SDs or TCH and
3. Tilt, HBA and Orientation should be verified from Audit Reports as per plan
If outage/fluctuation time matches with KPI degradation, then issue is most probably
possibility where previously handovers were being done to some particular cell,
where after congestion on that cell, handover to that cell will not be completed and
call on source cell will either be dropped or in try to handover to another cell (with
8. TA for all TRX need to be checked. Incase some TRX TA is much low can indicate it is
should be compared
Such issues can affect HSR, TCH ASR and DCR etc