Beruflich Dokumente
Kultur Dokumente
Version 1.00
ZTE CORPORATION
ZTE Plaza, Keji Road South,
Hi-Tech Industrial Park,
Nanshan District, Shenzhen,
P. R. China
518057
Tel: (86) 755 26771900 800-9830-9830
Fax: (86) 755 26772236
URL: http://support.zte.com.cn
E-mail: doc@zte.com.cn
LEGAL INFORMATION
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
The contents of this document and all policies of ZTE CORPORATION, including without limitation policies related to
support or training are subject to change without notice.
Revision History
Document
ZXG10 B8018 (V1.00) In-Door Base Transceiver Station Maintenance Manual (Troubleshooting)
Name
Document Revision
Product Version V1.00 R1.0
Number
Equipment Installation Date
Presentation:
(Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization,
Appearance)
Good
Fair
Average
Poor
Bad
N/A
Intelligibility:
(Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)
Good
Fair
Average
Poor
Bad
N/A
Please check the suggestions which you feel can improve this documentation:
Improve the overview/introduction
Make it more concise/brief
Improve the Contents
Add more step-by-step procedures/tutorials
Improve the organization
Add more troubleshooting information
Include more figures
Make it less technical
Your
Add more examples
Add more/better quick reference aids
suggestions for
Add more detail
Improve the index
improvement of
this
Other suggestions
documentation __________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
# Please feel free to write any comments on an attached sheet.
If you wish to be contacted regarding your comments, please complete the following:
Name Company
Postcode Address
Telephone E-mail
This page is intentionally blank.
Contents
Chapter 1.......................................................................... 1
Chapter 2.......................................................................... 5
Chapter 3.......................................................................... 9
Chapter 4........................................................................19
Chapter 5........................................................................29
Chapter 6........................................................................ 45
Loading Faults................................................................ 45
Software Version Cannot be Imported.................................... 45
Loading Failure ................................................................... 45
CMB/DTPB Board Unable to Start .......................................... 46
The Board Software cannot be Imported ................................ 46
Repeated Loading of CMB..................................................... 46
Repeated Loading of DTRU ................................................... 47
LAPD Link Establishment Failure after Software Loading ........... 47
FU LAPD and HDLC Disconnection Alarms ............................... 48
Chapter 7........................................................................ 49
Chapter 8........................................................................55
Service Faults.................................................................55
Overview ..................................................................... 55
Symptoms ......................................................................... 55
Troubleshooting ............................................................ 56
BTS Call Test ...................................................................... 56
Performance Analysis........................................................... 56
Signaling Procedure Analysis................................................. 57
Poor Signal Quality or Signal Fluctuation................................. 57
Frequent Call Drops due to Hard Handover.............................. 57
No Traffic in the Cell or Sudden Rise of Call Drop Ratio ............. 58
MS indicates Signal Fluctuation or No Signal............................ 58
System Prompts Failure to Connect........................................ 59
Strong Signals but Unable to Make a Call ................................ 59
Handover Failure................................................................. 60
Occupation of Carrier for Short Time ...................................... 60
The Carrier Cannot be Occupied ............................................ 60
Long SDCCH Occupation Time ............................................... 62
Sudden Rise of Call Drop Ratio .............................................. 62
BTS Overload Message ......................................................... 63
Low TCH Assignment Success Ratio ....................................... 63
Chapter 9........................................................................65
Appendix A .....................................................................69
CBA Parameter...............................................................69
CBA Parameter Modification .................................................. 69
Appendix B .....................................................................71
Appendix C ..................................................................... 73
Abbreviations ................................................................. 73
Appendix D ..................................................................... 75
Figures............................................................................ 75
Tables ............................................................................. 77
Index .............................................................................. 79
This page is intentionally blank.
About this Manual
Purpose
This Manual provides procedures and guidelines that support the
troubleshooting of ZXG10 B8018 Base Transceiver Station.
Intended Audience
This document is intended for engineers and technicians who
perform troubleshooting activities on the ZXG10 B8018 Base
Transceiver Station.
Chapter Summary
Chapter 1 Maintenance Introduces the safety measures that are
Safety taken during the troubleshooting process
Chapter 2 Maintenance Introduces the common troubleshooting
Overview methods
Chapter 3 Transmission Introduces the BTS faults caused due to
Faults transmission Failure
Chapter 4 Antenna Introduces the faults caused due to
Feeder Faults antenna feeder problems
Chapter Summary
Chapter 5 Voice Faults Introduces the analysis and
troubleshooting procedures of voice faults
Chapter 6 Loading Analyzes the faults that may occur during
Faults software loading process
Chapter 7 Clock Faults Analyses the clock synchronization
problems
Chapter 8 Service Analyzes faults such as weak signal, call
Faults drop, poor voice quality and handover
faults
Chapter 9 Board Faults Introduces the troubleshooting procedures
to solve board faults
Appendix A CBA Introduces the methods for modifying the
Parameter Modification CBA parameter
Appendix B DTMF Introduces principles of DTMF signal tone
Signal Tone Generation generation
Appendix c, Lists English abbreviations used in this
Abbreviations manual
Appendix D, Figures Lists all the figures used in this manual
Appendix E, Tables Lists all the tables used in this manual
Index Index for reference to different topics
Related Documentation
The following documentation is related to this manual:
ZXG10 B8018 Base Transceiver Station Documentation Guide
ZXG10 B8018 Base Transceiver Station Technical Manual
ZXG10 B8018 Base Transceiver Station Installation Manual
ZXG10 B8018 Base Transceiver Station Maintenance Manual
(Routine Maintenance)
ZXG10 B8018 Base Transceiver Station Maintenance Manual
(Troubleshooting)
Conventions
Typographical ZTE documents employ the following typographical conventions.
Conventions
Typeface Meaning
Italics References to other Manuals and documents.
Typeface Meaning
“Quotes” Links on screens.
Bold Menus, menu options, function names, input
fields, radio button names, check boxes, drop-
down lists, dialog box names, window names.
CAPS Keys on the keyboard and buttons on screens
and company name.
Constant width Text that you type, program code, files and
directory names, and function names.
[] Optional parameters.
{} Mandatory parameters.
| Select one of the parameters that are delimited
by it.
Note: Provides additional information about a
certain topic.
Checkpoint: Indicates that a particular step needs
to be checked before proceeding further.
Tip: Indicates a suggestion or hint to make things
easier or more productive for the reader.
Maintenance Safety
Safety Instructions
Only trained professionals must operate and maintain the
BTS equipment.
Follow the local safety codes when operating and maintaining
the BTS equipment.
Safety precautions used in this manual are only
supplementary to the local safety codes.
ZTE shall not bear any liabilities incurred by violation of the
universal safety regulations or violation of safety standards
for designing, manufacturing and usage of the equipment.
Safety Signs
The general safety signs used in this manual are listed in Table 4.
No flammables: No flammables
can be stored.
No smoking: Smoking is
forbidden.
Precautions
Equipment Strictly follow the Standard Operation Procedures (SOP) of
Operations the equipment.
Wear antistatic wrist strap when touching any hardware of
the equipment.
Never perform operations such as plugging/unplugging,
resetting, starting or switching, loading/modifying equipment
data without prior permission.
Virus Do not change the network settings and the settings of OAM
Protection for server or client without prior permission.
the System
Use CDs and disks provided by ZTE for installing software for
Operation and Maintenance (OAM) server or client.
Do not install and run any program irrelevant with operation
and maintenance on the OAM server or client.
Fault Report Detect the problems and faults and report major problems to
the relevant officials and the local ZTE office.
Record the detailed troubleshooting procedures.
Maintenance Overview
Troubleshooting Procedure
The troubleshooting procedure consists of four phases:
Fault Analysis
After collecting information about the faults, analyze the possible
fault causes.
Fault can be categorized as follows:
Transmission faults
Antenna feeder faults
Voice faults
Loading faults
Clock faults
Service faults
Board faults
This manual analyzes the faults based on the above fault types
and introduces the troubleshooting methods.
Fault Locating
After analyzing the fault causes, use various troubleshooting
methods to rule out the impossible fault causes and locate the
exact fault cause.
For detailed information regarding fault analysis methods, refer
to Common Fault Analysis and Locating Methods
Fault Removal
After locating the fault, take appropriate steps to remove the
fault and recover normal operation of the system.
Performance Analysis
Performance analysis is done through performance management
interface in the iOMCR.
Analyze performance measurement tasks, performance reports
and BSS performance indices, detect load distribution in the
network and adjust network parameters to improve the network
performance.
Signaling trace is done through signaling trace interface of
iOMCR to locate signaling faults.
Plug/Unplug
Upon detecting fault in a board, plug or unplug the board and
external connectors, in order to remove the faults caused by
poor contact.
In addition, remove the faults caused by poor contacts by
pressing the cable connectors.
Isolation
Isolate the faulty part from the other relevant board or rack, and
decide whether the fault cause is due to mutual influence
between them.
Self -Test
Judge a fault by observing the flashing of LEDs on the board
panel after the system or board is re-powered on.
Transmission Faults
OVERVIEW
Transmission faults may create the following alarms:
Broken LAPD link of a BTS site
Broken OAM link of a BTS site
E1 interface frame out of sync
E1 interface code slip notification
Troubleshooting
Transmission faults are mainly caused by the following:
Transmission bit errors
Time slot allocation problems
The basic troubleshooting steps for transmission faults are:
Performing bit error test
Checking E1 time slot (TS) allocation
Troubleshooting Reset the CMB board and check whether the fault is removed.
Conduct self-loop test and check if the physical link between
the BTS and BSC is broken.
Check the BSC, transmission equipment and BTS for any
fault.
Confirm if the DIP switch setting is correct and matches the
configuration data.
Troubleshooting Interchange the upper and lower level relations of the two
sites and check whether the problem is solved.
Check the equipment for faults.
Check the DIP switch setting.
Troubleshooting Observe and check for any alarm in DTRU and confirm its
normal operation.
Reset the DTRU and observe whether it can recover.
Upgrade the software to the latest version.
Troubleshooting Confirm the connections of the faulty BTS and check if the
equipment related to the BSC has the same problem.
Transmission failure
Troubleshooting Remotely reset the CMB to reset the BTS. If the system
indicates connection timeout, the communication link
between the iOMCR and the CMB of the BTS must be broken.
Check if there are alarms from all DTRUs in the BTS. If yes,
follow the steps below to troubleshoot the fault:
f Check if the E1 line is correctly connected.
f Check if the TIC and LAPD boards on the BSC report
alarms. If so, remove the corresponding fault.
f Measure the transmission Bit Error Ratio (BER) using a
BER tester. If BER is abnormal, remove the transmission
faults including transmission equipment faults and
grounding faults.
f Check whether the DIP switch on the TIC board is set to
an appropriate position.
Overview
Symptoms Voltage Standing Wave Ratio (VSWR) alarm
Poor uplink or downlink quality
Related Alarms iOMCR may indicate the following three types of alarms:
Major VSWR alarm of a Combiner
This alarm occurs when the VSWR value of the antenna
feeder system connected with the combiner is greater than
3.0.
Minor VSWR alarm of a Combiner
This alarm occurs when the VSWR value of the antenna
feeder system connected with the combiner is between 1.5
and 3.0.
LNA alarm of a divider
This alarm indicates that the divider is faulty.
Physical connections:
DTRUA1 - Combiner A - Antenna feeder A
DTRUA2 - Combiner B - Antenna Feeder B
Data configuration:
DTRUA2 - Combiner A - Antenna feeder A
DTRUA1 - Combiner B - Antenna Feeder B
Background combiner A1 reports a major VSWR alarm when
VSWR serious alarm occurs at antenna feeder A1. However, the
system blocks DTRU A2 due to data configuration error. DTRU
A1 still transmits power. In this case, Cell A does not support
normal calls due to big VSWR and neither Cell B because it is
blocked due to error.
Troubleshooting
Replacement 1. Replace the CDU that may be faulty with a normal CDU.
2. Check whether the antenna feeder system is normal.
3. Connect the antenna feeder system that may be faulty and
the normal CDU using a jumper.
4. If an alarm occurs, the fault lies in the antenna feeder
system. If not, the fault lies in the CDU.
Systematic Any one of the following problems may cause the antenna feeder
Check system faulty:
Improper installation of connectors
Improper sealing of connectors with water-proof
Damages in feeder or jumpers
High VSWR value of lightning arrestor
High VSWR value of antenna
Water enters the antenna
Check the antenna feeder system and replace the faulty parts if
necessary.
If a part does not satisfy the VSWR requirement, it must be
faulty. First, check the easily accessible parts before checking
the parts hard to reach.
If VSWR alarm occurs occasionally, then the problem may be
due to poor contact of cables.
Shake the parts to check the reliability of cable connection.
VSWR Faults
Symptom VSWR alarm (Minor or Major)
A minor VSWR alarm occurs when the VSWR value is
between 1.5 and 3.0 while a major VSWR alarm occurs when
the VSWR value is greater than 3.0.
Source Board LEDs
Background Operation and Maintenance System
Fault Analysis A CDU reports a major VSWR alarm when it has VSWR2 alarm
that lasts for one minute. Upon receipt of this major alarm, the
OAM automatically turns off the DTRU.
Coverage Shrinkage
Symptoms Output power of the BTS equipment decreases
Coverage shrinks after a period of time
Fault Analysis The aging and overload of devices may cause performance
deterioration.
Troubleshooting Measure the output power of the BTS and replace the AEM if
output power is abnormal.
Ensure that the operating temperature is within the specified
range.
Ensure that the latest version of software is in use.
Troubleshooting Check if the CDU reports any Tower Mount Amplifier (TMA)
alarm. If so, handle the fault in the way as handling a TMA
alarm. For details, refer to TMA alarm
.
Check if the CDU reports any Low Noise Amplifier (LNA)
alarm. If so, handle the fault in the way as handling an LNA
alarm. For details, refer to LNA Alarm
.
Check if the connection from the antenna input port on the
CDU to the cabinet top is normal. If the connection is
abnormal, replace the connection cable.
Check the VSWR of the antenna feeder systematically,
starting from the cabinet top.
Fault Analysis The following factors may influence the coverage of the BTS:
Poor BTS environment
Poor construction quality or maintenance of the BTS
Low PA output power
Decreased receiver sensitivity
Inclined azimuth
Altered antenna pitch angle
Altered gain and height
Feeder cable or combiner loss
Altered working frequency and transmission environment
Troubleshooting Replace the DTRU that may be faulty with a DTRU of a normal
cell. Check if the cell reports the same alarm.
There are the following possibilities:
If the cell reports alarm even after replacing DTRU, then the
problem may not be in DTRU. The problem may lie in PA,
antenna feeder or backplane.
Replace the boards to eliminate board faults.
If the cell does not report any alarm when DTRU is replaced,
then the fault lies in DTRU. Replace the faulty DTRU.
If the alarm of the problematic DTRU disappears and the
normal DTRU does not generate any alarm, then the fault
may be due to the poor contact of DTRU. If the fault remains,
then the fault may be in the threshold settings or other
hidden problems. In this case do further analysis to
troubleshoot the problem.
TMA Alarm
Symptom TMA alarm
Troubleshooting 1. Reset the CDU and check whether the TMA alarm
disappears. If the alarm does not disappear, it indicates that
the CDU misreports alarm. So replace the CDU.
LNA Alarm
Symptom LNA alarm
Fault Analysis An LNA reports an alarm when the LNA current exceeds 30%
more than the normal operating current.
Voice Faults
Troubleshooting
Users often report two-way blocking as one-way
conversation problems. So locate and determine the exact
problem.
Check whether the fault occurs to a single BTS or BSC or a
larger range.
If the fault occurs only to outgoing calls, check the
corresponding outgoing trunk and data. Check all the parts if
the fault lies within the local office.
Locate the fault by checking the hardware and data
configuration, assisted by dialing test.
If the fault is in BTS, perform drive test and record the
frequency and the timeslot occupied by a call, using test MS.
If the fault is in a module, perform A-interface circuit dialing
test, determine the trunk occupied by a call and locate the
relevant boards through interface message analysis.
For troubleshooting one-way conversation, make a call from
an MS to a fixed phone and determine whether the fault lies
in the uplink or downlink.
Fault Analysis RF faults may cause signal loss and poor call quality.
Fault Analysis The fault may be due to the wrong configuration of connection
relations, mostly incase of multiplexing.
One-way conversation
Symptom The calls can be dialed normally but only one party can hear the
voice of the other party.
Troubleshooting Check whether the fault occurs inside the local office or at
the interconnected systems. Perform dialing tests on the
trunk circuits to troubleshoot the problem.
If the fault occurs to the whole MSC, check whether the
equipment buyer or other relevant staff has reconfigured the
MSC data or performed relevant operations during cutover.
Check whether the transmitting and receiving ends of the
trunk line on the A-interface is connected properly.
If the fault occurs to the entire BSC or many BTSs of the BSC,
Check whether the DRT version is correct. If so, switch over
the active DSNI/BOSN with the standby DSNI/BOSN and
check whether the problem persists after the switchover.
If the fault occurs to only one BTS, verify the radio
parameters and check whether the maximum MS transmit
power is correct.
If the problem persists, do dialing test with a test MS to
confirm whether the one-way conversation problem is related
to a carrier timeslot or not.
If the problem always occurs to a certain carrier, replace the
corresponding AEM equipment. Ensure that the latest version
of software is in use.
Two-way Blocking
Symptom Neither party of the conversation can hear the peer party.
Troubleshooting First, second and fourth cause may lead to two-way blocking
of many BTSs. Troubleshoot according to the cause.
Third cause may lead to two-way blocking of single BTS.
Troubleshoot according to the cause.
If the problem always occur to a certain carrier and there is
no multiplexing, replace the corresponding AEM equipment
or connector.
Ensure that the software is upgraded to the latest version.
Fault Analysis The fault may be mainly due to faulty antenna feeder equipment
or software problem.
Poor voice quality is due to high voice BER at the radio
interface, which is caused by low receiving level, clock faults
or co-channel interference.
Low frequency level may be caused by the following factors:
f Inappropriate parameter configuration.
For example, the MS maximum transmission power
MSTXMAXCCH (power used during access) and MS
maximum transmission power MSTXPWRMAX (power for
power control) are inconsistent.
f Antenna feeder system faults, such as abnormal VSWR,
improper setting of azimuth angle, and pitch angle.
f Low BTS transmission power.
Crosstalk
Symptom The conversation party hears an unexpected third party voice.
Fault Analysis The fault may be caused when the transmitting and receiving
ends of transmission line are incorrectly connected.
Fault Analysis Apart from the phone quality and unstable performance caused
by the long use of the MS, the factors that influence the wireless
signal intensity of a place are as follows:
Environment
Unstable transmission power of DTRU
Cell reselection
Fault Analysis If the TCH and BCCH occupied by the MS does not belong to
the same carrier and the DTRU is unstable, it will cause the
MS to present strong signal in idle state and weak signal
during conversation.
Frequent MS handover (ping-pong handover) may cause
unstable MS signal during busy state.
Echo in MS Conversation
Symptom Echo occurs when the MS is in a conversation.
Typical Case
This section introduces the methods to locate the one-way
conversation problem in the GSM BSS network.
Fault Analysis
1. Determine the range of fault occurrence
Troubleshooting
1. Troubleshooting BTS fault
The troubleshooting steps for a BTS fault are as follows:
i. Check whether there is software mismatch in BTS boards.
ii. Check whether there is any abnormal BTS alarm.
iii. Delete the BTS hardware data and reconfigure the data
so as to eliminate data errors.
iv. Replace the problematic DTRU board and check whether
the fault is caused by DTRU.
v. Replace the CMB board and check whether the fault
disappears.
vi. Modify the data and connect the BTS to another BTS port
if another Abis interface exists, and check if the fault
disappears. If the fault disappears, replace the TIC board
and BIPP board in turn and find out the faulty board.
2. Troubleshooting BSC fault
i. Test
If the fault is detected in many BTSs, then the BSC must
be faulty. If there is coverage of the BSC in the
equipment room, perform frequency locking test using a
test MS. Otherwise install a test BTS for the test. Conduct
the test after 0000 Hrs so as to facilitate fault locating
and to avoid influence on subscribers.
Most of the one-way conversation problem is related to A
interface circuit. Conduct dialing test on the A interface.
ii. Record
Record the A interface CIC occupied by each call during
the test. Check whether the fault occurs and the fault
symptom is similar.
iii. Fault locating
BSC generally contains a central module and several
peripheral modules. Check and judge whether the fault is
related to all peripheral modules or a single peripheral
module. If the fault is related to one module, focus and
check the module and the cable connections between the
peripheral module and the central module. If the fault is
related to all peripheral modules, focus the check on the
central module and the A interface circuit.
iv. Board switchover
If the fault is suspected to be in the boards such as BOSN
and PP that has active/standby modes, perform board
switchover and check whether the fault lies in these
boards.
v. Board resetting
Many fault symptoms may disappear after board
resetting but avoid resetting the board before the fault is
completely located, because the fault may reoccur.
vi. A interface check
Two conclusions can be finally drawn from the dialing test:
f One-way conversation problem is related to the specific
circuit in the A interface.
f There is no fixed relationship between the one-way
conversation problem and the A interface circuit.
In the first case, if the one-way conversation problem
occurs to all the timeslots of a 2 Mbps circuit, then the A
interface circuit line may be cross connected with another
circuit line, as shown in Figure 2.
Summary
The causes for one-way conversation problem are summarized
as below:
Problems of the MS
The design, aging or faults of MSs may cause one-way
conversation problem.
BTS equipment problems, for example faulty timeslot of
DTRU or CMB board.
Problems of the Abis interface circuit, for example, an
individual timeslot embezzled by subscribers, faulty TIC or PP
board.
Problems of the connection cable between the peripheral
module and the central module, such as poor contact.
BOSN board problems.
Problems of the EDRT, TCPP, AIPP or TIC board, mostly EDRT
board problems.
Problems of the A interface. For example, incorrect cable
connection and cross-connection of wires.
Loading Faults
This chapter analyses the faults that may occur during the
software loading process.
Fault Analysis The fault may be due to the mismatch of version file name and
the internal ID.
Loading Failure
Symptoms Loading process keeps repeating.
BTS site keeps restarting and could not start normal
operation.
Fault Analysis Signaling analysis helps to locate the fault causes. The causes
are as follows:
Transmission errors, which causes reloading
Mismatch of software version with the hardware
Fault Analysis The fault may be due to the Mismatch of version ID and the
version name.
Troubleshooting Perform Abis signaling trace and check whether the loading
process is completed.
Check the data transmission if:
f The BTS does not respond in the loading process.
f Re-transmission of loaded data exceeds certain number
of times which leads to re-initiation of the loading.
If software loading is successful, but software fails to activate,
then check whether a correct version is loaded.
Fault Analysis The fault may be due to DTRU software version mismatch.
Troubleshooting Check the compatibility between the DTRU software version and
the hardware.
Fault Analysis The fault may be due to the mismatch of Software version
(CMB_FPGA).
Fault Analysis The fault is mainly due to the mismatch of software version and
the hardware.
Clock Faults
This chapter analyzes the problems that may occur during clock
synchronization.
Overview
Symptom
The symptoms for clock faults are as follows:
CMB alarm
DTRU alarm
Slow internet access of the MS
MS handover failure
Poor conversation quality of the MS
Fault Analysis
The main cause of a clock fault is that the BTS clock severely
deviates from the clock required for the normal running of the
BTS. The symptom is that the RF unit does not get a precise
clock.
The clock fault is caused by the following:
Inaccurate 13 MHz clock signal generated by CMB
Unstable 13 MHz clock signal generated by CMB
CMB is in synchronization with the external clock but the
clock reference received from the BSC is unstable
Faulty PLL of the DTRU
Poor contact of the clock cable with the CMB and the DTRU
PLL is deadlocked
Troubleshooting
Clock Module Reset/Restart
Reset the modules (CMB and DTRU) which had alarms.
Power off the modules (CMB and DTRU) which had alarms.
If it can be recovered through the above ways, it indicates
that the PLL is deadlock and hardware is normal.
Classified Faults
Symptoms Clock and frame number alarms
PLL clock loss
DSP WATCHDOG overflow
Slow internet access of the MS
Problem in handover
Poor voice quality
Troubleshooting Check the synchronization between the BTS and the BSC.
Check the clock locking function of the CMB board.
Clock alarms
Symptom Clock alarms and frame number alarms occur to the CMB and
DTRU
Troubleshooting Measure the CMB clock reference, check the transmission for
external synchronization and calibrate the CMB reference clock
for internal synchronization.
Fault Analysis PLL lock loss caused by unstable clock differs from the PLL
permanent PLL lock loss caused by hardware fault.
Fault Analysis The clock deviation causes bit errors and error frames during the
decoding process.
Fault analysis Onsite test results show that the frequency offset of 13 MHz
clocks of some BTSs is as high as 2.5 Hz (far more than the
standard value 0.65 Hz).
Many BTSs reports 8 kHz clock alarm.
MSC often reports the normal/abnormal phase locking of the
clock software alarm, indicating that the MSC clock is also
inaccurate. Therefore, it can be determined that the call drop
problem during handover may be due to the MSC clock
instability.
Fault Analysis An inter-BSC handover failure can be caused by either of the two
BSCs.
The fault may be due to the following:
Free running of adjacent BTSs of other vendors.
Big clock deviation of adjacent BTSs of other vendors.
Troubleshooting Adjust the clock working mode of the BTSs of other vendors.
Service Faults
This chapter analyzes the faults such as weak signal, call drop,
poor voice quality, and handover faults.
Overview
Symptoms
Service-related faults are the faults that occur to the call service
when the BTS does not give any alarm.
These faults include
Weak signal
Call drop
Poor voice quality
Handover failure
No traffic in a cell
Troubleshooting
BTS Call Test
Tools SAGEM MS or NOKIA test MS
Test Procedure In urban areas, dial calls at about 200-300 m away from the
antenna of each cell in the positive direction.
In suburban areas, dial calls at about 500-1000 m away from
the antenna of each cell in the positive direction.
Ensure that the call test cover each carrier.
Record the level and quality of the call on each timeslot of
each carrier.
Use Table 5 for the call test records.
TRX1
CELLID
TS0 TS1 TS2 TS3 TS4 TS5 TS6 TS7
CH
RXLEV
RQ
CH
RXLEV
RQ
Check After If any problem occurs to the receiving level or the voice quality
Test during carrier testing, handle the problem in time and ensure
that the equipment commissioning quality is good.
Performance Analysis
Generate a report that covers all performance indices. For voice
calls related problems, perform the following steps:
Check the interference band.
Check the uplink/downlink level.
Check the uplink/downlink quality.
Check SDCCH and TCH assignment time.
Check the assignment success ratio.
Troubleshooting Check if the GPRS services are activated in the particular cell.
Check whether the cell system messages indicate any GPRS-
related information.
Check whether the connection between the CDU and the RF
equipment is normal.
Check whether the output power is normal.
Call drop
Fault Analysis The fault may be mostly due to the failure of components inside
the TRX.
Fault Analysis Some MSs indicate CS signal fluctuation when the PS ATTACH
operation fails. This fault is mainly due to the GPRS
configuration errors.
Troubleshooting Check the GPRS configuration or disable the GPRS option of the
cell.
Fault Analysis The called MS may be attempting PS ATTACH. Most MSs may
not respond to the CS paging message when processing the PS
service, and as a result the network reports that the MS is not in
the service area.
Fault Analysis The BCCH of the cell fails and cannot receive any signal from the
MS.
Troubleshooting Reset the BCCH to solve the problem temporarily.
Upgrade the BTS software to the latest version.
Precautions When this problem occurs to a carrier other than the BCCH, that
carrier may have a high call drop ratio.
Handover Failure
Symptoms Week MS signal during conversation
MS does not perform handover operation until a call drop
occurs
Fault Analysis The fault may be due to the faulty hardware or its incorrect
connections.
Fault Analysis The fault may be mainly due to the equipment instability.
Fault Analysis The fault may lie in the hardware and its connection.
Troubleshooting Select an appropriate time when the traffic is low; Block all
TCHs of the other carriers except one TCH through dynamic
data management. Observe whether calls can be made
normally and then check the system until the faulty DTRU
and TCH are located.
If alarm occurs, handle the fault according to the alarm
information.
If no alarm, handle the fault as the following steps:
i. Check the RF cable connection between the DTRU and the
combiner of AEM, and the RF cable connections between
two receiving ends of the DTRU and the AEM divider
output port. If the RF cables are incorrectly connected,
connect the cables correctly.
ii. Reset the DTRU. If the problem persists, replace the
DTRU.
Board Faults
Fault Analysis The valid bits of Trunk node alarm are not in the default values
(zeros and ones). The recovery strategy may not work for trunk
node during BTS processing.
Troubleshooting Check whether the CMB board location is the same as in the
configuration.
Reset the CMB.
Clear the BSC alarm and get the alarm again.
Backplane Fault
Symptom The backplane has no corresponding alarm slots, but clock,
HDLC, LAPD or other faults may occur.
Troubleshooting Check whether the board is faulty. If the board is normal, the
fault lies in the backplane. Contact local ZTE office or ZTE
customer support center.
PA VSWR Alarm
Symptom A VSWR alarm occurs to the PA
CBA Parameter
This section deals with the modification of Cell Bar Access (CBA)
parameter.
Cell Bar Access option is not selected for normal cells. When it is
selected, common MSs will not be able to access the cell.
After modifying this parameter, find the corresponding CBA
option on the test MS and change the status into Reverted or
Disabled.
Abbreviations
Figures