Professional Documents
Culture Documents
OMD6072 Case Analysis - Congestion ISSUE1.1
OMD6072 Case Analysis - Congestion ISSUE1.1
Case Analysis—Congestion
ISSUE1.1
Wireless Curriculum
Development Section
Summary
=(TCH call occupation failure times+very early assigned TCH occupation failure
times)/(TCH call occupation request times+very early assigned TCH occupation
request times)*100%.
Basic Principle of TCH Congestion Ratio
Channel_Active
Channel_Active_Ack
first SABM
Establish_IND( CM Service Req)
CR(Complete_l3_information)
CC
CM Service Accepted
Setup
Call Proceeding
Channel_Active Assignment_Req
Channel_Active_Ack
ASSIGNMENT COMMAND
SDCCH first SABM
Establish_IND
SDCCH
UA
SACCH(TCH)
ASSIGNMENT CMP
SACCH(TCH) Assignment_CMP
Alerting
Connect
Connect Ack
communication
Disconnect
Release
Release Complete
Clear_CMD
Clear_CMP
A interface
After MSC sends Assignment_req, If trunk circuit at A
interface is fault, BSC will return Assignment_refuse directly.
In this case, the usually cause is incorrect CIC data
configuration of trunk circuit.
Basic Principle of TCH Congestion Ratio
Through the traffic statistic “Cell TCH Performance Measurement”, check whether TCH
congestion is attributed to all busy status. If yes, perform traffic equalization or suggest
the equipment buyer to expand the capacity.
If the congestion is not due to all busy status, analyze whether it is caused by
interference. Check interference bands 1~5. In the cell affected by interference, the
drop ratio will be high.
Register “Receiving Performance Measurement” traffic statistic task:
1. Check the measurement result by object to see whether the numbers of
uplink/downlink reports on the same TRX board are balanced. Thus you can know
whether the uplink/downlink hardware tributaries on the board are balanced.
2. Check the measurement result by time to see whether TRX measurement reports are
excessive in a cell. Thus you can know whether the congestion is related to the board.
Cause of High TCH Congestion Ratio and
Locating Method
Check alarms of the site in the cell where there is high congestion
ratio. Check whether there is any abnormal alarm, such as
standing wave ratio alarm, PCM OOF alarm and uplink data bus
alarm. Judge whether the congestion ratio is associated with
alarms with traffic measurement .
Cause of High TCH Congestion Ratio and
Locating Method
Trace ABIS message of the congested BTS, analyze Assignment CMD sent by SDCCH and judge
whether the assignment always fails on a specific TRX board.
If the assignment always fails on a specific TRX board, the cause may be one of the following:
If the assignment fails on the RC boards of the whole cell randomly, analyze the measurement
reports. The causes may be the following:
Perform local maintenance and check to see if there are abnormal alarms. If
yes, process it promptly.
Perform a dial test with the test mobile phone in the same place to see
whether the assignment failure always occurs in one frequency or is randomly
distributed.
Make driving test to see whether there is abnormal handover relation and
downlink interference, so as to find the real cause of the congestion ratio.
Case 1
Fault description: There is one BSC in the local network. And from one day
on, TCH congestion ratio of the whole network begins to rise (frequency
planning was not changed). TCH congestion ratio of the whole network (not
including handover) is 4%(the congestion ratio on all busy is very low). In
addition, many cells but not a few cells are highly congested.
Cases of TCH Congestion Ratio Problem
Case 1
Analysis:
1. Since the frequency plan is not adjusted, radio interface
problem is ruled out.
2. Congestion ratio is abnormal in most BTS. In this case,
search in a smaller range to see whether the congestion
problem is related to module or data modification.
3. Analyze the main cause of TCH occupation failure
through traffic statistic and finally locate the problem as
data or hardware fault.
Cases of TCH Congestion Ratio Problem
Case 1
Troubleshooting:
1. View the traffic statistics . The problem occurs after BSC data are modified and loaded. Maybe it is
related to BSC loading.
2. Analyze traffic statistics to find that the highly congested cells are focused on module 1 of BSC.
Then the problem should be with module 1.
3. Check the module to find that TCH occupation failure is mainly attributed to unavailability of
terrestrial resources. It shows that unavailability of terrestrial resource is the main cause of high
congestion ratio in module 1.
4. The cause of terrestrial resources unavailability is mainly on the circuit of Abis interface or A
interface. This problem occurs to many cells in module 1. However, it is quite unlikely that Abis
interface is faulty in many cells at the same time. Therefore, the cause should be the hardware or data
at A interface.
5. Check the hardware of A interface to find that the hardware is normal. A interface hardware problem
is ruled out.
6. Check the data configuration of the trunk circuit of A interface to find that the CIC code of the first 32
timeslots of group 0, module 1 is 65535. But group 0 of module 1 in the trunk group table corresponds
to the circuit from BSC to MSC. Obviously this CIC number is wrong. Change it to 0~31 and set
dynamically, and then the congestion ratio is lowered to normal.
Cases of TCH Congestion Ratio Problem
Case 1
Conclusion:
1. In trunk circuit data configuration at A interface, CIC must be
correct, otherwise, TCH assignment will fail and the congestion
ratio will be high.
2. In the meantime, if the CIC of two FTC boards (multiple trunk
circuits) are the same, this problem will also happen.
Cases of TCH Congestion Ratio Problem
Case 2
Case 2
Analysis:
1. No data have been adjusted and there is no hopping in the cell. 6
TRX use different bands. It is unlikely that they are subject to
external interference at the same time. Therefore, it can not be Um
interface interference or data problem.
2. Check hardware specifically. Since the problem only occurs to cell
1, we can block TRX in turn to determine which TRX causes the
assignment failure.
3. Find out whether there is hardware fault in the TRX for assignment
failure. Check them one by one by means of resetting and replacing.
Cases of TCH Congestion Ratio Problem
Case 2
Troubleshooting:
1. Check BT channel status through remote maintenance and find that there is
possibility of TCH occupation failure in BT4, BT5 in cell 1.
2. Block BT4 and BT5 as well as RC4 and RC5 at the same time and find that there is
no TCH congestion all the day. It indicates that the problem is on RC4 and RC5.
3. Unblock BT4, BT5, RC4, RC5, and reset RC4(TRX4), RC5(TRX5) and high congestion
arise again.
4. Go to the BTS site and make a dial test with the frequency locked (on TRX4, TRX5),
TCH occupation failure still occurs. Exchange the slots of TRX4 and TRX5 and make
the dial test again (TRX4, TRX5). The TCH occupation failure persists.
5. Replace TRX4, TRX5 and make dial test with the frequency locked (on TRX4, TRX5),
TCH occupation is successful and there is no TCH congestion. The problem is solved.
Cases of TCH Congestion Ratio Problem
Case 2
Conclusion:
1. The faulty TCH TRX board causes TCH assignment failure and
high congestion ratio.
2. Usually, the fault of TRX board can not be found on the BTS
maintenance console . The problem can be confirmed by
blocking in turn.
Cases of TCH Congestion Ratio Problem
Case 3
Case 3
Analysis: There is no interference but congestion always exists after the BTS is in
service, in every cell. But other BTS has no such problem, therefore, check hardware
of the BTS.
1. Hardware fault: communication is normal in every cell, so it is unlikely that there is
fault in the hardware of every cell.
2. Hardware connection: Check hardware connection carefully. Analyze the traffic
measurement to locate whether the fault is in the uplink or the downlink and then
check the hardware connection of the uplink or the downlink.
Cases of TCH Congestion Ratio Problem
Case 3
Troubleshooting:
1. Register traffic statistics “Receiving Level Measurement Function” and
query the result of traffic statistics by time. It is found that when the receiving
level and receiving quality of different TRX boards in the same cell are the
same, the number of downlink measurement reports is balanced but the
number of uplink measurement reports is not, regularly unbalanced.
2. Check and find that the connection of TRX and CDU in the same cell is
incorrect. After correction, the problem is solved.
Cases of TCH Congestion Ratio Problem
Case 3
Times of uplink Times of uplink Times of Uplink receiving
receiving level receiving level grade 0 level grade 0 and receiving
grade 0 and and receiving quality quality level 2
receiving quality level 1
level 0
Case 3
Conclusion:
Incorrect hardware connection will cause TCH assignment
failure. The problem can be located accurately by analyzing
different traffic statistics tasks.
In this case, uplink hardware receiver problem is located
through “Receiving Level Performance Measurement”.
Cases of TCH Congestion Ratio Problem
Case 4
Case 4
Case 4
Troubleshooting:
1. Trace ABIS interface message of the BTS with a signaling analyzer MA10 and analyze the
signaling to find that in process of TCH assignment failure, the uplink signal in the
measurement report from the MS is of high quality after BSC sends ASSIGNMENT CMD, but
the downlink signal level can not be resolved, i.e. the levels of uplink/downlink signals are
not balanced. Then ASSI FAILURE message is returned. It is also found that the assignment
is directed to the last TRX board in the cell.
2. Block the TRX board channel temporarily and congestion ratio of the cell is lowered to 1%.
Perhaps there is problem in TRX board and the downlink hardware.
3. Check and find that the Transmitting antenna&feeder VSWR is over 2.5 alarm on the
combiner connected with TRX board. Process the antenna&feeder VSWR alarm and the
problem is solved.
Cases of TCH Congestion Ratio Problem
Case 4
Case 6
Case 6
Case 6
Troubleshooting:
1. Block TRX of the last two newly added TRX on the remote BTS maintenance console to find that
the congestion ratio is lowered to normal status. Perhaps, the problem is related to the two boards.
2. Trace and analyze ABIS interface signaling to find that the assignment failure occurs to the two
newly added TRX. When the assignment fails, SDCCH measurement report analysis shows that the
level on SDCCH is normal and TA value is large and the assignment takes place in a distant area.
However, there is no measurement report on SACCH (TCH). Perhaps the two boards have hardware
problem in uplink/downlink tributaries. Sometimes the assignment of the two boards succeeds, so
the boards could not be faulty.
3. A 4 in 1 combiner and a splitter are used in the cell, the antenna & feeder part can not have a
hardware fault. Check the cable from TRX board to the combiner/splitter and no hardware problem is
found. Basically it can not be a hardware problem.
4. It is told that this cell is attached with a repeater. After the expansion, the repeater did not lock the
two newly added TRX, which causes the assignment failure. When the repeater band problem is
solved, the congestion problem is also solved.
Cases of TCH Congestion Ratio Problem
Case 6
Conclusion:
Because of the repeater, the coverage areas of the first two
TRX and the last two TRX in the same area are different,
which results in the assignment failure.
Cases of TCH Congestion Ratio Problem
Case 8
Case 8
Case 8
Troubleshooting:
1. Register “Incoming Inter cell Handover Measurement Function” for 15 minutes
in the two cells to find that all the handovers from a specific cell
(CGI=*********1768) to these two cells fail, and the handover is not the actual
cause of congestion.
2. Failure of all handovers means that there is problem with the handover data.
Check the handover data of the two cells to find that there is co-frequency and
co-BSIC as expected. The two cells are adjacent to the specific cell, therefore the
handover from the specific cell to any other cell will fail. The failure occurs when
TCH channel is assigned.
3. Modify the BCCH and BSIC of the two cells, and then the handover is
recovered and congestion ratio is normal.
Cases of TCH Congestion Ratio Problem
Case 8
Conclusion:
1. Two cells (both adjacent to a specific cell) with co-frequency and
co-BSIC will not only result in low in-cell handover success ratio, but
also high TCH congestion ratio (including handover).
2. The case indicates that TCH congestion ratio (including handover)
and TCH congestion ratio (not including handover) are different.
Cases of TCH Congestion Ratio Problem
Case 9
Case 9
Analysis:
1. Since the congestion ratio is not very high, the problem may not be on
the data or hardware.
2. The interference band is normal, so the interference at the Um
interface is unlikely.
3. Analyze the cause of assignment failure. Take dropout ratio into
consideration and analyze the receiving performance of uplink/downlink,
including level, quality.
Cases of TCH Congestion Ratio Problem
Case 9
Troubleshooting:
1. View “Dropout Performance Measurement” to find that TA value is large upon
dropout, at a distance of 25.6km~31.1km away from the BTS.
2. View “Receiving Level Performance Measurement” to find that there are many
measurement reports of low level grades.
3. Analyze ABIS signaling to find that the uplink level is very low (about –98dbm)
when the assignment fails.
4. Make a driving test on the site to find that the site is isolated, with large
coverage and complicated topography. When the MS is more than 25 kilometers
away from the BTS, it can receive –90dbm downlink signal. But the uplink signal
is not enough, so TCH assignment fails.
Cases of TCH Congestion Ratio Problem
Case 9
Conclusion:
1. Poor uplink coverage causes the high congestion ratio.
Adding BTS can help form a continuous coverage.
Change the omni-directional site into a directional site
by adjusting the antenna angle. Intensify the transmitting
level and BTS receiver sensitivity. Avoid over coverage.
2. Trace Abis port message on the BTS maintenance
console to analyze the assignment status.
SDCCH Congestion Ratio
Channel Required
Policy: expansion
【Conclusion】:
For SDCCH congestion due to location updating, check
whether it is caused by improper setting of location area.
This case is a special one. Add SD or enable dynamic
allocation function to solve the problem.
Cases of SDCCH Congestion Ratio
Problem
Case 3
【Fault description】
Deploy a BTS30 base station. After the deployment, SDCCH channel is
always in all busy status (A). TCH channel is in (I) or (A) status. When
the call is connected, the communication is normal. Observe the traffic
statistics and find that the SDCCH assignment of traffic statistics fails
about 1000 times (in busy hours).
Cases of SDCCH Congestion Ratio
Problem
Case 3
【Analysis】:
1. Since SDCCH is congested after the BTS deployment, but TCH and
communication are normal. First check data and hardware. The whole site
suffers from congestion problem. Swap ports with other sites of the same
type to confirm whether there is data problem or hardware problem under
Abis interface.
2. If data problem and hardware problem are ruled out, attention should be
focused on the transmission problem.
Cases of SDCCH Congestion Ratio
Problem
Case 3
【Troubleshooting】
1. Check alarm: LAPD link fault alarm and recovery alarm (within one second). The alarm
appears once per ten minutes.
2. Check the data to find no problem. At night, exchange with BIE port of other BTS of
the same type, other sites work normally but problem of this site persists. Data problem
and BSC side hardware problem are ruled out.
3. Since the BTS is far from the city , first register the transmission related traffic
measurement . Observe the result (related to transmission) and find no problem, but
SDCCH traffic measurement remains abnormal.
4. Replace TMU and TRX board in the BTS and the problem persists.
5. Measure the transmission and self-loop BIE, then It is found that there is bit error in
the transmission. Test the line section by section and find that in a segment of access
network from a county to the BTS, one 2M transmission board is faulty. Replace the
board and the problem is solved (the two BTS are on the same board).
Cases of SDCCH Congestion Ratio
Problem
Case 3
【Conclusion】:
The causes of SDCCH congestion can be :
1. Data configuration error
2. SDCCH channels insufficient
3. Um interface problem (interference, low level, uplink/downlink unbalance)
4. Hardware fault
5. Transmission quality problem
In this case, the cause is item 5 mentioned above. Due to transmission bit error, large
number of data are lost at SDCCH assignment or data are resent many times to
timeout after the data loss. This causes the occupation failure and hence the high
congestion.
Cases of SDCCH Congestion Ratio
Problem
Case 4
【Fault description】
A complaint is received that mobile subscribers near 4 sites (ABCD) of a local
network can not make calls, but there no related alarm information on the alarm
maintenance console.
1. Check the 4 BTS, the board status is all normal. Almost no TCH channel is
occupied. Sometimes one TCH is occupied, it becomes idle in several seconds. All
SDCCH channels are in A status.
2. It is learnt that .BTS-A is attached under it with BTS-B and BTS-C. BTS-D, using a
primary combiner (a transmission timeslot multiplexer), shares a 2M transmission
line with BTS-A.
Cases of SDCCH Congestion Ratio
Problem
Case 4
【Analysis】
The symptom can help judge whether the problem is on the hardware or
on the transmission. But it is unlikely that faults occur to hardware of the
4 BTS. The transmission lines of the 4 BTS are related, therefore, check
the transmission carefully.
Cases of SDCCH Congestion Ratio
Problem
Case 4
【Troubleshooting】
1. Carefully observe 32BIE indicator to find that the indicator flashes every 12 seconds. It indicates
that there is bit error in the transmission. Check the microwave and optical transceiver and no
abnormal indication is found.
2. Check ABIS interface signaling to find that a large number of PAGING_CMD messages are
generated. Among them, one RF_RESORCE_INDICATION message is generated occasionally.
There is no CHAN_ACTIV, CHAN_ACTIV_ACK or IMMEDIATE_ASSIGN_COMMAND message. It
indicates that SDCCH channel is not activated.
3. Check data O&M log, and find no data modification has been done in a few days in the past.
Therefore data problem is ruled out.
4. Check the indicator of corresponding ports of 32BIE and find that the indicator is off. It seems
that the transmission is normal.
5. Reload and activate the board software of BTS-ABCD, and find that the system response is slow,
even with communication timeout prompt. When the board is loaded and activated, SDCCH is still
congested. Users still complain that they can hardly call out. Since the 4 sites share one 2M
transmission line and SDCCH occupation is abnormal at the same time, it is concluded that it is
transmission problem.
Cases of SDCCH Congestion Ratio
Problem
Case 4
【Troubleshooting】
6. The only transmission equipment in doubt after the resetting --- primary
combiner (resetting causes the re-initialization of ABCD). After ABCD
initialization is complete, and it is found that SDCCH are fully occupied and TCH
can be occupied normally. Trace ABIS interface signaling, CHAN_ACTIV,
CHAN_ACTIV_ACK or IMMEDIATE_ASSIGN_COMMAND message appears.
SDCCH is no longer congested. Users on the site say that they can make calls
normally.
7. The same problem may occur to the primary combiner, therefore the operator
is recommended to use optical transmission circuit. After the modification, the 4
BTS have been running normally.
Cases of SDCCH Congestion Ratio
Problem
Case 4
【Conclusion】: