1.1.

1 Analysis and Processing Call Drop Problem in the Case of PN

Multiplexing 030929 zhang Chao
[No.]
0024835
[Latest change date]
2003.09.29
[Prepared by]
Li Zhongdong
[Phenomenon description]
When locating the call drop problem in area A, the onsite engineer in a certain site finds that the
problem is related to the system PN multiplexing.
[Alarm information]
None.
[Processing]
The problem disappears after the onsite engineer configures the correct neighbor relationship and
longitude and latitude.
[Cause analysis]
From the tracing and result, there are at least two errors in the whole call drop process:
1. Call drop owing to judging the BSC neighbor cell wrongly: Distribute No. 17 BTS 400Km
away to MSs in area A as their current service BTS.
When a MS detects a wrong neighbor cell and reports it to the BSC through the PSMM, the BSC
cannot directly detect the correct BTS through the PN that is multiplexed in the system. To solve
this problem:
a) Configure correct neighbor cells of the BTS. So that the BSC can detect
the correct BTS based on the PN through the neighbor cell relationship.
b) Because the system detects the PN based on the longitude and latitude,
the BSC can correctly detect the PN based on the longitude and latitude of
the BTSs. At present, the system requires that the PN multiplexing
distance must be more than 10KM by default.
2. Call drop caused by masses of reverse error codes owing to the wrong judgment:
Before the call drop, the main pilots in this area are main branch 236 judged from the signaling.
Further, the BSC has not received any PMRM from any MS before the call drop. Therefore, the
main branch here is in perfect condition. At this time, however, a mass of reverse error code
appears, resulting in call drop. The BSC or MS may cause the problem.
[Related document]
Remark of case reviewer: Because the problem still exists in the current RO2BO3D008 version,
the onsite engineer must pay attention to checking the onsite data of R02B03 version first. Check
whether the switch of the neighbor cell that is not configured is off. If no, add correct longitudes
and latitudes to each BTS, small BTS, and soft BTS as mentioned in the above case.
[Attachment name]
2015-6-10

1 , 5

Analysis and Processing in Case of PN Multiplexing Zhang Chao 333

[Suggestion and summary]
To locate and dig up the problem, you can adopt the method of signaling analysis and processing,
which is an important method during the network optimization..

1.1.2 Low Network Quality Due to Pilot Signal Search Failure Caused by
Incorrect PN Planning 020610 Sun Jing
[No.]
0019322
[Latest change date]
2002.06.10
[Prepared by]
Deng Yubin
[Phenomenon description]
Upon activation of certain office, it is found that the Ec/Io of signal is week through drive test.
Sometimes, there is even no strong pilot nearby the BTS. Through multiple drive tests, it is found
that the PN offset in certain sectors never occurs. Further, all these PNs are all in sector 2, and they
are not integral multiple of 4.
[Alarm information]
None.
[Processing]
Re-update the PN planning of sector 2 of all BTSs. Plan the PNs to integral multiple of 4 (such as
152, 156...), and then import the scripts for loading. The problem is solved.
[Cause analysis]
When the PILOT_INC is set to 4, the search window of the MS only searches the PN offset that is
integral multiple of 4 (such as 4, 8, 12504, and 508). This is determined by Qualcomm chip.
The MS cannot search other pilots. The PNs of all sectors 2 are planned from 150 (that is, 150,
154, 158). All the neighbor pilots vary four PNs, complying with PILOT_INC=4. However,
compared with sector 1 (4, 8, 12) and sector 3 (300, 304, 308...), the PNs of sector 2 are not
integral multiples of 4. Therefore, the MS can only search the pilots of sectors 1 and 3. Because
the MS does not search the pilots of sector 2, the signals in sector cannot be used.
[Related document]
None
[Attachment name]
PN Planning Example.zip
[Suggestion and summary]
When the PILOT_INC is set to 4, only integral multiple of 4 (0, 4, 8, 12... 504, and 508) can be
used for PN planning. Where, value 0 is generally not used. This is determined by Qualcomm
chip. At present, most of the CDMA phone manufacturers use the Qualcomm chips. For the BTS,
2015-6-10

2 , 5

the problem does not exist. The reason is that the BTS only searches the active set signals reported
by the MS. All the PNs in the active set are valid ones. Actually, from the definition of
PILOT_INC, if the PN is within (1, 5, 9...505, and 509), or (2, 6, 10...506, and 510), or (3, 7,
11...507, and 511), it is also reasonable. However, as restricted by Qualcomm chips, the sequence
(4, 8, 12504, and 508) is only used.
In this case, the PN of a certain sector is not the PN within the sequence. Therefore, the MS cannot
search these pilot signals.
The general PN planning principles are as follows:
1. Avoid adopting neighbor PN offset for different sectors in the same BTS.
2. Avoid adopting neighbor PN offset for neighboring BTSs.
3. To re-use PN, the distance between sectors must be more than 6R (R represents the radius of the
cell).
The attachment provides an example of PN planning (PILOT_INC=4). It is typical.

1.1.3 Call Drop Due to Too Short PN Reuse Distance after Frequency
Shift
[Document number]
SC0000178172
[Update date]
2005-12-26 14:26:46.0
[Author]
Wang Wenzheng
[Problem description]
A CDMA450 MHz network uses frequency 160 and 260. The wireless committee took back
frequency 160, so the office must shift to frequency 210 from frequency 160.
After the frequency shift, according to traffic measurement, high call drop rate is present in
frequency 210 of sector 2 in BTS-139. Generally, the call drop rate is about 5%, and sometimes, it
is up to 10-plus percent. The indexes of frequency 260 of sector 2 in the BTS-139 are normal.
[Alarm information] None

[Cause analysis]
1.
This problem is caused by too short PN reuse distance. Before the frequency shift, BTS-139
uses frequency 160 and 260, and BTS-173 uses frequency 210. They have the same PN, but the
frequency is different, and they work normally. After the frequency shift, BTS-139 uses frequency
210 and frequency 260. At that time, sector 0 of BTS-139 and sector 0 of BTS-173 use frequency
210 and the same PN, and the LOS between two BTSs is close. In this case, soft handoff is
established by mistake and calls are dropped.
2.
PN100 of sector 0 of BTS-173 is added to the neighbor cells of 0 sector of BTS-113, and
PN100 of sector 0 of BTS-139 is added to the neighbor cells of sector 2 of BTS-139. When a
handoff is conducted between sector 0 of BTS-113 and sector 2 of BTS-139, the system combines
neighbor cells. When the system finds two same PN100, it delivers one PN100. At that time, the
system deletes PN100 of sector 0 of BTS-139. The delivered PN100 is the PN100 of sector 0 of
BTS-173. When the MS searches PN100 of sector 0 of BTS-139, the MS reports the message to
system through PSMM. However, the system mistakes the PN100 as that of BTS-173. Therefore,
the system establishes a traffic channel on BTS-173. The Ec/Io of PN100 of sector 0 in BTS-139
2015-6-10

3 , 5

is stronger and stronger. When the MS combines each branch, the branch with strongest Ec/Io
does not establish a traffic channel. Errors will be present on power control bit, and MS Tx power
decreases. Consequently, the MS fails to receive traffic frames from MS and many error codes are
generated, and C05 call drop is present.

[Handling process]
1. Extract CSL data of BTS-139 and find that cause values of most calls drop are C05. The call
drop is related to BTS-173. The C05 call drop is present when Ec/Io and forward FER are normal.
CSL records are detailed below:
<CSL> ,5,213,c05,7,1,7fc1,10,ffff,acb,acc,ade,ffff,ffff,81e,f89,460068950101895,3ad0f5af,6,2a,0,
013989009815,8b,2,8b,2,210,3,500c4400,fa,0,82,6,84,0,1270,3,139,2,12,16,182,1,31,29,173,0,22,
16,224,96,0,930,0,, [2004-12-15 09:25:34.510];
The following are displayed from the CSL:
AccCell: 0x8b(BTS-139)
AccSector: 0x2 (2 sectors)
DropCell : 0x8b(BTS-139)
DropSector: 0x2 (2 sectors)
CdmaFreq: 0x210 (frequency 210)
ActivePnNum: 3
PN1.Cell: 139
PN1.Sector: 2
PN1.Strength(-0.5dB): 12
PN1.Delay (Chip(s)): 16
PN2.Cell: 182
PN2.Sector: 1
PN2.Strength((-0.5dB)): 31
PN2.Delay(Chip(s)): 29
PN3.Cell: 173
PN3.Sector: 0
PN3.Strength (-0.5dB): 22
PN3.Delay (Chip(s)): 16
FwdFER: 0 (0%)
RevFER: 930 (93%)
We can find that the call drop is due to high reverse FER when forward Ec/Io and forward FER
are normal and there are three soft handoff branches.
2. The call drop rate at frequency 210 of sector 2 of BTS-139 increases after frequency 210 is
shifted to frequency 210. Check the BTS data in the areas before and after frequency shift, and
find that both PN of sector 0 of BTS-139 and PN of sector 0 of BTS-173 are PN100. The LOS
between BTS-139 and BTS-173 is 16km and they are separated by BTS-113 only. Therefore, we
doubt that the call drop rate increases because of too short PN reuse distance.
The information of BTSs are as follows:
a. BTS-139 is of S222 site, and uses PN100, PN268 and PN436. Before the frequency shift, BTS139 uses frequency 160 and frequency 260. After the frequency shift, BTS-139 uses frequency
210 and frequency 260.
2015-6-10

4 , 5

b. BTS-113 is of S111 site and uses PN132, PN300 and PN468. Before and
after frequency shift, BTS-113 uses frequency 210.
c. BTS-173 is of O1 site and uses PN100. Before and after frequency shift,
BTS-173 uses frequency 210.
3. We conduct a CQT in the overlay coverage areas by sector 2 of BTS-139
and sector 0 of BTS-113. On the artery, we go along with the BTS-139
downtown, and the call drop is present almost each time. The symptom is:
When PN100 is in active set, Ec/Io is better and better, MS Tx power
decreases largely or changes, and the call is dropped. According to CSL
records of testing MS at system side, we find that when the call is dropped,
the branch is established on PN100 of BTS-173.
4. Modify the PN of BTS-173 and ensure enough PN reuse distance. When PN100 of BTS-173 is
changed to PN164, the problem is solved.

[Suggestions and summary]

1.
If the frequency shift is required, we must consider the PNs of surrounding BTSs to avoid
the call drop due to the same frequency and too short PN reuse distance after the frequency shift.
2.
Currently, Huawei system can add two neighbors with the same PN to a carrier. In this case,
soft handoff branch is established by mistake and calls are dropped, the call drop rate is very high.
It indicates that error tolerance of Huawei system is not perfect and we should improve Huawei
system. When the neighbor cells are added, two same PNs are prohibited for the neighbor cells of
a carrier.
3.
In the case of neighbor combination, if there are two same PNs, the system should record
abnormal log or alarms.

2015-6-10

5 , 5