Professional Documents
Culture Documents
ZTE university
Training goals
To know the causes of speech quality problems and problem handling procedures.
Contents
Monologue Cross-talk Bidirectional Silence Poor Speech Quality Echo
MonologueCauses
Wireless part BTS (software& hardware)
MS
External interferenc e
Causes of monologue
Abis interface
We can tell if its an inter-office or intra-office problem from subscribers feedback and call test
If its an intra-office problem, find out if the problem is with some BSCs or all BSCs under the MSC Find out if the problem is with some sites or all sites under a BSC.
Check corresponding outgoing trunk and data. As for problems inside the office, check all parts in the problem area.
Try to find out if customer or other relevant personnel made changes on MSC data or performed operations during site swap.
first check if the version of BSC DRT is upgraded to be able to solve monologue problem if the version is right, change over the active and standby DSN boards of BSC; make test after the changeover to see if the problem still exists. When analyzing and locating this problem, we can open the GSM subscriber interface trace at MSC maintenance platform, make circuit dialing test at A interface; with the interface message, analyze the trunk occupied by the problem call, calculate the corresponding single board to check the boards and connection wires (all single boards and connection wires between E3M and NET, including backboards).
check cells radio parameters, whether UL/DL power link is balanced or not (collect data through signaling tracing), whether MS max transmission power is set correct or not. make call test and check hardware to find out if hardware problems exist, such as equipment connection problem, TRX fault, combiner fault, antenna fault, etc.. further confirm the problem is about UL or DL with MS calling landline phone.
Problem analysis
ZTE engineers went to the site and made call test.
Intra-office call test
CALL TEST between MSs inside the office, both MOC and MTC were under the same BSC (BSC4) ;MOC was under BSC4, and MTC was under BSC11; no monologue problem occurred in both situations.
Confirmed: trunk circuit data were configured wrong during the expansion and swap of Telecom outgoing circuits.
End
Problem solved
Problem analysis
Engineers made DT and CALL TEST on site; Among the 50 times of CALL TEST, monologue or two-way silence occurred about 15 times.; Through observing the situation of MS seizing frequency and timeslot, engineers found that monologue occurred when MS seized a frequency of a cell; The MS receive level fluctuated greatly, which even reached 30dB, as shown in the following figure.
Problem handling
When the defective TRX was replaced, engineers made CALL TEST again and monologue problem disappeared, and the problem didnt occur in the following days.
Problem handling
Engineers went to the site and made call test, finding the monologue problem was related to the level. When DL level was under 80dBm, metallic noise and monologue appeared in calls. It was also found in call test that UL speech quality was poor, while DL speech quality was good, so the monologue was due to UL problem. After checking OMCR data, engineers found that interference band of BCCH 113 and TCH 99 in BTS A was very serious, the interference class even reached 5.
Contents
Monologue Cross-talk Bidirectional Silence Poor Speech Quality Echo
Crossed-wires at A interface; incorrect exchange of timeslots made by timeslot multiplexing equipment when the equipment is used in transmission; wrong configuration of BTS data .
If cross-talk appears during intraoffice calls, check if there are crossed wires at A interface first; If cross-talk appears during interoffice calls, check if there are crossed wires in outgoing office circuits ; Block the E1 equipment that uses timeslot multiplexing device, and make test, so as to check if the problem is caused by timeslot multiplexing equipment fault; As for dealing with cross-talk at one BTS, focus on checking of BTS transmission, hardware and data configuration.
Connected the faulty E1 to BSC1 and MSCA, the crosstalk problem continued.
4
Changed EDRT board of the corresponding slot in BSC1 with a new one, the problem disappeared, no monologue or cross-talk happened;
3
Changed DTI board of the corresponding slot in MSCA with a new one, the problem continued
Problem analysis
Made call test on site; Its discovered that cross-talk occurred when MS occupied BCCH timeslot2 of a cell under the site; while no similar problem happened to other timeslots of other TRXs; Changed the faulty TRX, but cross-talk still existed.
it is suggested that the operation (change of channel types) be performed in integrated configuration management, so as to avoid data configuration mistakes.
Contents
Monologue Cross-talk Bidirectional Silence Poor Speech Quality Echo
Transmission circuits are selflooped; The CIC codes at the two sides of the circuit do not meet with each other; Some timeslots of the transmission circuit adopted are not good; In the shared E1, timeslot multiplexing equipment is not configured with timeslots correctly; DRT/EDRT or TIC fault.
First locate the problem area, make certain if the problem is prevalent in most sites or it just appears in some sites; If the problem is prevalent, we can refer to cause 1, 2 and 5, and make investigation accordingly; If the problem just exists in some sites, we can refer to cause 3 and 4, and make investigation accordingly.
Problem analysis
From the problem phenomena, it was certain that the problem existed widely in most sites. Engineers made call test on site.
The root cause of the problem is maintenance peoples incorrect manipulation (during expansion and swap of BSC A interface).
Continued call test Found problem
Confirmed single board fault, check the board and wire connection
Problem disappeared
Problem solved
Contents
Monologue Cross-talk Bidirectional Silence Poor Speech Quality Echo
Methods of handling poor call quality First locate the problem area, make certain if the problem is prevalent in most sites or it just appears in some sites; If the problem is prevalent, we can refer to cause 2, 4 and 5, and make investigation accordingly; If the problem just exists in some sites, we can refer to cause 1 and 3, and make investigation accordingly.
Problem analysis
Subscribers who lodged complaint were scattered in different counties, which meant that the problem was prevalent in most BTSs. Phenomena of on-site test: When dialing or receiving calls, the party at the BTS area could hear the counterparty, but couldnt be heard. This meant that there was something wrong with the BTS UL signal, which was reflected in on-and-off speech, trembling voice accompanied with high current hum or background noise.
Problem handling:
Made call test to all DSP of each EDRT in the BSC, found out and replaced the faulty EDRT, the problem was solved.
Problem location:
Faulty DSP chips of BSC EDRT single boards resulted in disorder in code conversion and rate adaptation and poor speech quality.
Problem analysis
Since the problem subscriber complained was in a single site area, engineers tentatively confirmed the cause was BTS fault.
Problem handling
During the call test metallic knocking suddenly appeared and it lasted for 30 seconds and then disappeared. In this process, the MS remained busy. Engineers carried out call test on TRXs one by one, and finally found one faulty TRX. While the problem didnt disappear even after the faulty TRX was replaced. When clock cable of the TRX was replaced, the problem disappeared.
Problem analysis
No BTS hardware fault: in test with YBT250, no UL interference was detected. Result of call test: when both MOC and MTC were under the site, the two parties could hear the same noise. When making calls with PSTN, only the PSTN terminal could hear the noise, it was normal with MS side. At V1 sites, no noise appeared. While the same problem happened to calls at V2 sites. Summary: Cause of background noise should be wrong data configuration or discrepancy in BTS or BSC versions.
Problem handling
After blocking UL power control and UL DTX of V2 site in OMCR, no background noise was detected. BTS V2 and BS30 (12M) could lead to the appearance of background noise. In the future version 12O, this kind of problem will be solved.
Contents
Monologue Cross-talk Bidirectional Silence Poor Speech Quality Echo
Echo problemPhenomena
Two types of echo:
Generally speaking, echo means one party can hear his/her own voice apart from the counterpartys voice during calls between digital MSs or between digital MS and landline phone. Another kind of echo-the loopback of voice means one party can hear himself/herself but not the counterpartys voice, while the counterparty can not hear anything during calls between digital MSs or between digital MS and landline phone.
Voice loopback
Voice loopback
Voice loopback
Collect the MS type; Use speech monitor; Judge MS isolation performance, export explanatory document.
Voice loopback
focus on finding out route data of the calls and make certain that the data are correct; when route data are configured right, check the EC configuration of mobile network equipment to make sure the EC is correct.; If the problem occurs during inter-office calls, we need to check if there are crossed-wires in outgoing office circuits.
Voice loopback
Find out MSC call list according to number and time of call; Make call test to all intra-office and inter-office trunks one by one; Check the faulty trunk circuit according to CIC.
Problem analysis
After checking large number of complaint letters and performing call tests, its certain the problem was about voice loopback. One party could only his/her own voice, but the counterpartys voice; the counterparty could hear nothing. The problem only appeared under MSC 04.
Start
End