Technical Document
File No.:
Version : A
Totally 27 pages
(Including the cover)
Standardized by
Approved by
ZTE CORPORATION
This document contains proprietary information of ZTE Corporation and is not to be disclosed or
used except in accordance with applicable agreements.
Secret ▲
Update Record
File No. Version Drafter / Update Reason Major Points Modified
No. Modifier Date
A Hongwei 2007.12.1 null null
Gao & 9
Chun
Chen
remark:The first time the file is edited, “Reason” and “Major Points Modified” shall be vacant.
2
This document contains proprietary information of ZTE Corporation and is not to be disclosed or
used except in accordance with applicable agreements.
Secret ▲
Catalog
3
This document contains proprietary information of ZTE Corporation and is not to be disclosed or
used except in accordance with applicable agreements.
Secret ▲
Guide
1.1 Procedure
Upon receiving the complaint of high SDCCH assignment failure, extract performance report
from OMC-R Client, filter out trouble cells based on SDCCH assignment failure rate.
(2) Check whether BCCH Trx of the bad cell share the same Lapd with that of other
cell’s BCCH Trx. If it’s the case, make a BCCH shift to other Lapd board to avoid
the multiplexing.
(3) Check whether there’re cells that use the same BSIC and same BCCH; If it’s the
(4) Observe one day. If the problem still exists, take the next step.
(5) Collect measurement report of the bad cells and get to know the time span of high
(6) Analyze basic measurement report. If counter 11687(Number of other access request
is zero, it’s probable that TCH handover request of other cell is mistaken for access
request of serving cell. If Mplog file contains the error message “Channel
interference, check whether there is the cell with the same BCCH and BSIC.
(7) Analyze basic measurement report, check whether counter 11643(Number of sdcch
allocation failures including handover) has value, if so then we may suspect for
(8) Analyze basic measurement report to see whether high SDCCH assignment failure
4
still exists. If it’s the case then check whether TCH assignment failure rate is high
This document contains proprietary information of ZTE Corporation and is not to be disclosed or
used except in accordance with applicable agreements.
Secret ▲
too. Generally TCH assignment failure rate is lower than SDCCH assignment failure
rate. If TCH assignment failure rate is high, it suggests that the cell is having some
coverage. If TCH assignment failure rate is good, observe signaling tracing of the
cell for 10 minutes, convert it to be MA10 format and filter Channel Request
messages. If there are many Immediate Assign failure of Channel Request with high
between TA of channel required and actual coverage range). For overlapping, adjust
BCCH transmission power or coverage range of the cell; For false signaling access,
(9) If SDCCH assignment failure increases suddenly, check whether it is periodic (High
SDCCH in fixed time of each day), if it’s the case then the coverage area is blind
spot.
(10) When SDCCH assignment failure increases suddenly but not periodic, confirm
whether it’s accompanied by TCH assignment failure. If it’s the case then the cell
(11) If SDCCH assignment failure is suddenly increased instead of periodic and without
accompanied with sudden high TCH assignment failure, check counter 11686 (LOC
access attempt times), counter 11638(LOC access success times) and counter
and counter 11638 is close to counter 11645 then most probably failures are caused
GSM network..
as follows
TS number S S
TxInteger represents (CCCH not combines with (CCCH combines with
SDCCH) SDCCH) 5
This document contains proprietary information of ZTE Corporation and is not to be disclosed or
used except in accordance with applicable agreements.
Secret ▲
3, 8, 14,50 55 41
4, 9, 16 76 52
5,10,20 109 58
6,11,25 163 86
7,12,32 217 115
Abis one-way signaling transmission delay is 60ms~100ms. For your notice,delay of one
240ms.
But if transmission link delay is large and TxInteger is inappropriately set, for example if Tx
integer is set to 15 it corresponds that the interval between two-channel request is about
300ms. Ie. MS resends Channel Request before receiving Imm Assign. At the same time
when MS sents the second attempt for channel request it receives Channel Request Imm
Assign of the first attempt and complete access procedure, during this process the Channel
(1) If Lapd1*4 multiplex is adopted, it’s probable that multiple BCCH share the same
lapd which will lead to great lapd throughput and finally time delay.
(2) Large lapd flow results in delay. For example, inappropriate LAC allocation will lead
(3) Transmission equipment has great delay. For example, ABIS adopts satellite
transmission.
(4) PS effect. PS is sensitive to network delay. If lapd has delay, PS message will be
resend which will add to the throughput and finally results in lapd delay and so on
If lapd delay reaches certain degree which leads to MS resending Channel Request, SDCCH
7
This document contains proprietary information of ZTE Corporation and is not to be disclosed or
used except in accordance with applicable agreements.
Secret ▲
MS BTS BSC
Channel Request
Channel Required
Channel Active
TxInteger
Lapd
Channel Active Ack Delay
Channel Request(Re-Send)
Channel Required
MS Imm Assign
change to Imm Assign(OK) Cmd
SDCCH Channel Active
Channel Active Ack
Imm Assign
Imm Assign(Fail) Cmd
(1) Two cells sharing BCCH & BSIC: Channel Request sent by MS is received by two
cells simultaneously and is assigned by SDCCH. MS can only provide access of one
Firstly six-bit color codes are added to the original eight information bits. These six-
bit color codes are generated by (BSIC and six-bit parity codes) mode 2.
Co-BCCH and co-BSIC may make BTS decode it as MS initial access of other site,
random access signaling (8bit and BSIC), two cells of same bcch and bsic may
(2) When one cell uses the BCCH same as other cells TCH/BCCH and CO-BSIC,
during the time of handover, “ handover access” message happened in the TCH TS
will be decoded by both the targeted cell as well as other cell that uses the same
BCCH/BSIC and so the cell which is not the original target cell will also decode as
Channel Request message. Hence the case will result in great SDCCH assignment
failure.
requests are not continuous. According to the protocol, if handover access message
sent by MS is the same with random access request message in format(AB frame)
continuous. If BCCH of one cell shares the same frequency with TCH of another
cell, handover access on TCH can be considered as random access request, which
will lead to SDCCH assignment failure. For checking these type of problem we can
analyze the signal trace, when we find RA is the same, TA is same while FN is
continuous. Thus we can conclude that great number of Channel Request is false
Thus if the two cell share the use the same BCCH and is close, downlink interference may
(1) Coverage area is large leading to poor downlink reception quality of cell edge.
Because sensitivity of BTS is high than that of MS, BTS can receive Channel
(2) Cell coverage is large which results in co-BCCH and co-BSIC with the cell far away.
control purpose. TA_allowed can also be used to solve the problem but it may cause MS to
fail to get access to the network. Therefore, threshold of TA_allowed shall be greater than
actual coverage range of the cell. Repeater influence shall be taken into account when
TA_Allowed. We do experiment concerning this problem and the result is when MS selects a
cell with strongest power . If TA_allow area update is unsuccessful, MS will select another
cell with less strong power(C1>0)access of this cell is allowed. Interval of cell reselection is
decided by TX_Integer and maximum resend time and is generally several seconds.
Remark: Other manufacturers have similar parameters like TAallowed. For example, Nortel
assignment by making the parameter link to actual coverage area range and setting proper
threshold to filter false RACH request. It shows that for cells with small radius coverage,
demodulate the noise to be RACH burst by mistake is almost 30% of all RACH requests.
signaling with less sensitivity has noise interference, which will definitely lead to SDCCH
assignment failure.
RACHMin(-dbm) is a parameter set to filter noise signaling. Random access signaling with
receiving level lower than RACHMin will be discarded as noise interference. By adjusting
False noise access signaling reflects in two aspects: 1- receiving level is week, 2- TA is
greater than actual coverage range. Hence RACHMin integrated with TA_allowed can
Notice: RachMin shall be carefully set. If it’s too high, it may affect paging success rate.
Request sent by MS, and MS can’t receive Imm Assign sent by BTS.Especially when MS is
put in pockets or under the pillows. If MS needs to do location update, Channel Request may
be frequent launched which will result in SDCCH assignment failure because Imm Assign
We discover that ZTE BSC3 SD assignment success rate is relatively low in a certain place
while analyzing its performance parameters and the rate is especially low on late busy hour,
2. Analysis
(1) After checking statistic we find out that almost each cell’s SD assignment failure
rate is high, and the bad assignment isn’t caused by cell’s radio parameters;
(2) We can see that SD channel has no congestion generally from statistic, the
(3) ZTE BSC1/2/4 SD assignment success rates are all above 95%, that’s a normal
after contacting China Unicom we find out that SD assignment success rates of all
BSC controlled by MSC7 (including Siemens BSC) are about 60%, and MSC7
paging success rate is also low. We get to know from China Unicom that there is
only one LAC controlled by MSC7. We have to page all cells in LAC while paging,
Contact Siemens and ask them to add one more LAC to MSC7 and update LAC SN of
cells controlled by part of BSC (Siemens). After the adjustment, BSC3 SD assignment
There are total 4 sites, TBT-G, TBT-D, GWD-G and GJR-G,all of which are controlled by
BSC01 but by different periphery modules. From the following performance parameter
form we can see that these sites’ SD assignment failure rates are as high as 50% or even
higher.
Object CI LAC FreqBand CellName SDCCH
ASS Failure
Rate
2. Analysis
We record signaling on Abis interface of TBT1, 4, 5, 6, GAR and GWD. Set TBT5 signaling
(1) We can see that the average time required to successfully activate one channel
is 0.58s.
(2) We figure out from the following signaling whether the two signaling is
12
This document contains proprietary information of ZTE Corporation and is not to be disclosed or
used except in accordance with applicable agreements.
Secret ▲
We can calculate frame numbers of the two channels by T1, T2 and T3. The
Tracking the whole process of the first channel request we can see it is a
complete signaling process to turn off the mobile phone. Tracking the whole
process of the second channel request we can see immediate assignment failure,
BSC doesn’t receive Establish Indication message, and T3101 is overtime and
The two signaling has the same Access delay: 3. Meanwhile the max retransmission
any mobile phone to send two Channel Require messages in one call is a random one
from 217 to 248 timeslot, which means the shortest interval between two requests sent
The interval between these two Channel Require messages received by BSC is 1.906-
between BTS and BSC are the same, then signaling length of the whole immediate
According to upper calculation of frame number, the real interval between these two
messages is 227 frames (1048), and then we deduce that the two Channel Require
3. Conclusion
We have to use satellite to transmit because these sites are far away from the urban area. The
satellite transmission delay on one direction is around 260ms, and then transmission delay
India accompanied with lots of TCH assignment failures. Basic measure data are shown
failure. After checking mpLog print we find out that the site has lots of LAPD Errors
get printed: “Site 36, BTS 3, TRX 2 catch errorF: receive SABME in Mulframe or
14
This document contains proprietary information of ZTE Corporation and is not to be disclosed or
used except in accordance with applicable agreements.
Secret ▲
TimerRec”, “Site 36, BTS 1, TRX 0 catch errorF: receive SABME in Mulframe or
Therefore we can confirm that there is transmission problem that causes lots of LAPD
breaks.
2.2 High SDCCH assignment failure rate caused by other signals with the same
BCCH and the same BSIC
2.2.1 Case 1
1. Problem description: In a place the high SDCCH assignment failure rate problem hasn’t
been solved for a long time, and SDCCH assignment failure rates of lots of cells in the
2. Solution: The problem can’t be solved by replacing all the hardware. When TA=20, a
signal from another cell with the same frequency and the same BSIC is received that
causes SDCCH assignment failure. Therefore we re-plan over 10 cells’ BSIC in the
whole network. After re-planning, parameters of all cells whose BSIC has been
3. Conclusion of fault analysis: Within 5km, if a mobile phone locates in an area covered
by two cells with the same BCCH and the same BSIC, then SDCCH assignment failure
may occur. The failure is triggered by these two cells with the same BCCH and the
15
This document contains proprietary information of ZTE Corporation and is not to be disclosed or
used except in accordance with applicable agreements.
Secret ▲
same BSIC, two cells’ SDCCH timeslots are synchronous. After mobile phone
synchronizes with BTS and chooses to be accessed into one of these two cells, it will be
4. So we have two solutions for high SDCCH assignment failure problem (within a certain
multiplexing distance, high SDCCH assignment failure rate caused by other signals
1) Reset cell’s CMM whose assignment failure rate is high, reset clock to avoid
temporary solution. In field situation we shall modify parameters and then change
2) The basic solution is to avoid signal with same frequency and same BSIC.
2.2.2 Case 2
1. Problem description: SDCCH assignment failure rate keeps high in a cell in Indian
spice network, but its TCH assignment rate is normal. Basic measure data are shown in
2. Problem Analysis: after tracking signaling of troubled cell, we find out that SDCCH
16
This document contains proprietary information of ZTE Corporation and is not to be disclosed or
used except in accordance with applicable agreements.
Secret ▲
We figure out that there is a cell 20Km away using same frequency and BSIC after
Analysis conclusion: Indian Spice doesn’t have much frequency resource and its sites
distribute densely, therefore it is inevitable that cells use same frequency and BSIC
within 34km. We have to change antenna down tilt angle or modify TA_Allowed to
shrink cell’s coverage, so as to solve SDCCH assignment failure caused by cells use
table shows the cell’s basic data measured on April 26th busy hour.
Time Alias 11644(Number 11645(Number
of SDCCH of SDCCH
Assignment Assignment
Successful) Failure)
follows:
SN TA Reason Time when immediate
assignment being
sent
1 6 location update 05-49-52.640
2 7 location update
3 7 location update
4 6 MTC
5 5 location update
6 5 MTC 05-56-43.343
7 0 MTC 05-57-24.531
8 4 MTC 06-00-02.109
9 1 MTC 06-00-02.890
10 63 MOC 06-05-56.828
11 61 MOC 06-06-12.656
12 59 MOC 06-06-23.578
13 5 location update 06-06-43.078
14 53 MOC 06-06-57.718
15 49 location update 06-07-22.578
16 46 MOC 06-07-42.718
17 43 MTC 06-08-08.515
18 41 MOC 06-08-14.765
19 40 MTC 06-08-20.578
20 18 Call reset 06-08-22.203
21 38 MOC 06-08-27.546
22 36 location update 06-08-45.062
23 5 MTC 06-08-52.140
24 5 MTC 06-08-52.625
25 34 MOC 06-08-52.796
26 5 MTC 06-08-53.281
27 35 MOC 06-08-55.375
28 36 MTC 06-08-55.562
29 35 MOC 06-08-55.984
30 34 MTC 06-08-56.578
31 32 MOC 06-09-11.640
32 30 MTC 06-09-24.546
33 27 MTC 06-09-38.031
34 27 MTC 06-09-38.578
35 27 MTC 06-09-39.109
36 0 MOC 06-09-57.171
37 24 MOC 06-09-57.828
38 10 MOC 06-11-15.406
39 2 MOC 06-12-12.781
40 0 MOC 06-12-52.671
18
This document contains proprietary information of ZTE Corporation and is not to be disclosed or
used except in accordance with applicable agreements.
Secret ▲
41 0 MOC 06-12-53.218
42 1 location update 06-15-13.140
The surrounding sites of the site distribute densely with distances lesser than 1km. TA
values are unreal on the table, we suppose there are fake signals. Further more,
2.3.2 Noise signal is represented as receiving level is lower than BTS receiving sensitivity
1. Problem description: a cell’s SDCCH assignment failure rate keeps high but TCH
level can be reported in physical context by Channel Request. Through observing the
cell’s signaling tracking data, we find out there are lots of Channel Request messages
whose receiving level is -135dbm ( 0x87 ) which cause large numbers of SDCCH
assignment failures.
19
This document contains proprietary information of ZTE Corporation and is not to be disclosed or
used except in accordance with applicable agreements.
Secret ▲
We can confirm that most of these Channel Requests are noise signal; we can solve it
2.4 High SDCCH assignment failure rate because frequency of target channel
to hand over is the same with that of BCCH of the problem cell, and target
cell has same BSIC with that of problem cell
2.4.1 Case 1
Problem description: the following are a cell’s signaling. We can see that there are
continuous Channel Requests with same RA, TA, and their frame numbers are consecutive.
All of the SDCCH assignments corresponding to these Channel Requests are failed with no
exception. Besides, “other access request attempt times” in basic measurement are
extremely high. Then we can confirm that all these abundant and consecutive Channel
20
This document contains proprietary information of ZTE Corporation and is not to be disclosed or
used except in accordance with applicable agreements.
Secret ▲
2.4.2 Case 2
A cell’s SDCCH assignment failure rate soars on busy hour, but TCH assignment failure rate
access whose Channel Request RA and TA are the same and frame number are consecutive.
21
This document contains proprietary information of ZTE Corporation and is not to be disclosed or
used except in accordance with applicable agreements.
Secret ▲
We find out there is a cell uses same frequency and same BSIC 14km away from the site
after checking frequency planning. The problem is solved by re-planning the frequency.
with high TCH assignment failure rate. Outgoing handover attempts are frequent and call
drop rate is high. Customer has complaints about it. The problem isn’t solved after resetting
Problem analysis: we can see from the cell’s basic measurement report that access reasons
are various for SDCCH assignment failure, both MOC access and MTC access account for a
certain proportion. The number of uplink sampling whose RQ > 3 is quite large, uplink
quality is very bad. Therefore we can confirm that the cell’s uplink signal has interference or
22
This document contains proprietary information of ZTE Corporation and is not to be disclosed or
used except in accordance with applicable agreements.
Secret ▲
2.5.2 Case 2
Problem description: a cell’s SDCCH assignment failure rate reaches as high as 58% on
busy hour, accompanied with 56% TCH assignment failure rate, handover success rate is
only 20%. After tracking signaling we find out there are lots of consecutive Channel
23
This document contains proprietary information of ZTE Corporation and is not to be disclosed or
used except in accordance with applicable agreements.
Secret ▲
Problem analysis: after checking the cell’s performance data of these days, we find out that
its TCH assignment failure rate, call drop rate and handover failure rate keep high but
without any alarm. DT engineer discovers that not only the cell’s own coverage is bad, but
2.5.3 Case 3
A cell’s SDCCH assignment failure rate reaches as high as 20% on busy hour.
UserLabel Object identifier Cell and Location Pmdatatime SDCCH TCH
Area Cell(LAC-CI) assign Assignment
failure Success
rate Rate
NANJANGUD-1 Bsc36-Site19-Bts1 LAC1036-CI36191 2007-12-17 10.8 81.75
20:00-21:00
NANJANGUD-1 Bsc36-Site19-Bts1 LAC1036-CI36191 2007-12-17 21.52 85.32
21:00-22:00
NANJANGUD-1 Bsc36-Site19-Bts1 LAC1036-CI36191 2007-12-18 18.28 82.17
20:00-21:00
NANJANGUD-1 Bsc36-Site19-Bts1 LAC1036-CI36191 2007-12-18 22.24 84.7
21:00-22:00
TCH assignment failure rate is as high as 20% while SDCCH assignment failure rate rises.
These two parameters are ok when traffic is low, which means the cell’s has downlink
24
This document contains proprietary information of ZTE Corporation and is not to be disclosed or
used except in accordance with applicable agreements.
Secret ▲
assignment failure rates soar without any rule, but meanwhile cell’s other parameters are
normal.
The following are signaling and basic measure data recorded when SDCCH assignment
failure rate is high. We can see from signaling that the reason for one MS keeps sending
access attempts is Channel Request due to location update, but all attempts are failed.
25
This document contains proprietary information of ZTE Corporation and is not to be disclosed or
used except in accordance with applicable agreements.
Secret ▲
hits 30% on busy hour. But other parameters (such as TCH assignment failure rate,
Channel Request messages of the cell commonly appearing together (with same TA and for
same reason). The Imm Assign corresponding to the first Channel Request is successful, but
26
This document contains proprietary information of ZTE Corporation and is not to be disclosed or
used except in accordance with applicable agreements.
Secret ▲
Set colored messages in the upper figure as an example; the FN of the first Channel Request
message is 964, the FN of the second Channel Request message is 1086, the FN difference
is 124. While Tx-Integer=12. Then we can confirm these two Channel Request messages are
sent by one MS. Because there is a certain delay on transmission link, then MS resends
Channel Request.
The cell’s SDCCH assignment failure rate decreases lower than 10% after changing Tx-
27
This document contains proprietary information of ZTE Corporation and is not to be disclosed or
used except in accordance with applicable agreements.