CDMA RNO Subject-Neighbor Planning and Optimization Guidelines - R1 (1) .0

CDMA Neighbor Planning and
Optimization Guidelines
R1.0
CDMA Neighbor Planning and Optimization Guidelines
Internal Use Only
LEGAL INFORMATION
By accepting this certain document of ZTE CORPORATION you agree to the following terms. If you do
not agree to the following terms, please notice that you are not allowed to use this document.
Copyright 2011 ZTE CORPORATION. Any rights not expressly granted herein are reserved. This
document contains proprietary information of ZTE CORPORATION. Any reproduction, transfer,
distribution, use or disclosure 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.
and
are registered trademarks of ZTE CORPORATION. ZTEs company name, logo
and product names referenced herein are either trademarks or registered trademarks of ZTE
CORPORATION. Other product and company names mentioned herein may be trademarks or trade
names of their respective owners. Without the prior written consent of ZTE CORPORATION or the
third party owner thereof, anyones access to this document should not be construed as granting, by
implication, estopped or otherwise, any license or right to use any marks appearing in the document.
The design of this product complies with requirements of environmental protection and personal
security. This product shall be stored, used or discarded in accordance with product manual, relevant
contract or laws and regulations in relevant country (countries).
This document is provided as is and as available. Information contained in this document is subject
to continuous update without further notice due to improvement and update of ZTE CORPORATIONs
products and technologies.
ZTE CORPORATION
Address:
NO. 55
Hi-tech Road South
ShenZhen
P.R.China
518057
Website:
http://dms.zte.com.cn (Technical Support)
Email:
TSM.Aftersales@zte.com.cn
ZTE Confidential Proprietary
2011 ZTE CORPORATION. All rights reserved.
Internal Use Only
Revision History
Product Version
ZXC10 BSSB V8.0.2.007 and
NetNumen M3 V3.08.20.07
Document Version
Serial Number
R1.0
Reason for Revision

First published
Author
Date
2011-03-29
Document Version
R1.0
Prepared by
Wu Yun
Reviewed by
Zeng Zhi, Liu Xun,
and Gu Fengyan
Approved by
Wu Yun
II
Internal Use Only
Intended audience: CDMA RF engineers
Proposal: Before reading this document, you had better have the following knowledge and skills.
SEQ
Knowledge and skills
Reference material
Basic theory of the CDMA technology
Null
Signaling flow of handoff
Null
Operation practice of ZTEs CDMA

NetNumen
Null
Follow-up document: After reading this document, you may need the following information
SEQ
Reference material
Information
CDMA 1X Multi-Carrier Network

Optimization Guide
A guide to the optimization of CDMA 1X

multi-carrier networks
NetMAX Operation Guide
A guide to the NetMAX operations
Hard Handoff Optimization Guide
A guide to the optimization of hard handoff
Configuration Parameter Manual (1X

Release A)
A guide to the configuration parameters (1X

Release A)
III
Internal Use Only
About This Document

Summary
Chapter
Description
Overview
Introduces the document briefly, including its objectives and

scope, the acronyms, and the email address for technical
support.
Basic Concepts
Describes the neighbor lists in CDMA 1X and EVDO systems.
Principles for Neighbor Planning
Describes the basic principles for neighbor planning.
Neighbors for IFHO (CDMA 1X)
Describes the neighbors for IFHO in CDMA 1X systems.
Neighbors for IFHO (EVDO)
Describes the neighbors for IFHO in EVDO systems.
Neighbors for Inter-BSC Handoff
Describes the neighbors for inter-BSC handoff in CDMA 1X

and EVDO systems.
7 Neighbor Optimization on the

NetNumen
Describes neighbor optimization operations on the

NetNumen.
Describes some other useful functions.
Other Useful Functions
IV
Internal Use Only
TABLE OF CONTENTS
1
1.1
1.2
1.3
1.4
Overview ......................................................................................................... 1
Objectives ......................................................................................................... 1
Scope ............................................................................................................... 1
Acronyms ......................................................................................................... 1
Technical Support ............................................................................................. 3
2
2.1
2.1.1
2.1.2
2.1.3
2.1.4
2.1.5
2.2
2.2.1
2.2.2
Basic Concepts............................................................................................... 4
CDMA 1X System ............................................................................................. 4
Linkcell ............................................................................................................. 5
NLCS ................................................................................................................ 6
NLIFHO ............................................................................................................ 9
Global NL ....................................................................................................... 10
Relationship Between the Above Four Types of Neighbor Lists ...................... 12
EVDO System ................................................................................................ 12
NLCS .............................................................................................................. 13
Global NL ....................................................................................................... 14
3
3.1
3.2
3.2.1
3.2.2
Principles for Neighbor Planning ................................................................ 16

Basic Principles .............................................................................................. 16
Practice of Neighbor Planning ........................................................................ 16
Theoretical Model ........................................................................................... 16
Real Case ....................................................................................................... 18
4
4.1
4.1.1
4.1.2
4.1.3
4.1.4
4.1.5
4.1.6
4.2
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
Neighbors for IFHO (CDMA 1X) ................................................................... 19

DAHHO and MAHHO ..................................................................................... 19
Applicable Scenarios ...................................................................................... 19
Triggering Conditions...................................................................................... 21
Configuration Steps ........................................................................................ 26
NLIFHO (DAHHO) Planning and Optimization ................................................ 33
NLIFHO (MAHHO) Planning and Optimization................................................ 35
Inter-Band IFHO ............................................................................................. 36
Pilot Beacon ................................................................................................... 37
Applicable Scenario ........................................................................................ 37
Neighbor Planning for IFHO (Pilot Beacon) .................................................... 42
Optimization.................................................................................................... 43
5
5.1
5.2
5.2.1
5.2.2
5.3
5.3.1
Neighbors for IFHO (EVDO) ......................................................................... 46

Applicable Scenario ........................................................................................ 46
Triggering the OFS ......................................................................................... 46
Idle state ......................................................................................................... 46
Conversation State ......................................................................................... 46
IFHO Area ...................................................................................................... 47
Internal Use Only
5.3.2
5.3.3
5.3.4
5.4
5.5
Threshold Parameter Setting .......................................................................... 47

Trigger Algorithm ............................................................................................ 48
Flowchart ........................................................................................................ 49
Neighbor Planning and Optimization for MAHHO ........................................... 51
6
6.1
6.1.1
6.1.2
6.1.3
6.2
6.2.1
6.2.2
6.2.3
Neighbors for Inter-BSC Handoff ................................................................ 52

CDMA 1X System ........................................................................................... 52
Introduction of the Configuration Interface ...................................................... 52
Planning ......................................................................................................... 57
Optimization.................................................................................................... 60
EVDO System ................................................................................................ 62
Configuration .................................................................................................. 64
Planning ......................................................................................................... 66
Optimization.................................................................................................... 66
7
7.1
7.1.1
7.1.2
7.2
7.2.1
7.2.2
Neighbor Optimization on the NetNumen ................................................... 68

CDMA 1X System ........................................................................................... 68
Optimization Without Handoff Statistics .......................................................... 68
Optimization With Handoff Statistics ............................................................... 74
EVDO System ................................................................................................ 83
Optimization Without Handoff Statistics .......................................................... 83
Optimization With Handoff Statistics ............................................................... 85
8
8.1
8.2
Other Useful Functions ................................................................................ 87

Neighbor Locking and Unlocking .................................................................... 87
Neighbor Sequence Sorting ............................................................................ 88
VI
Internal Use Only
FIGURES
Figure 2-1 Hierarchical Network Structure ............................................................................ 5
Figure 2-2 Schematic Diagram for an NLCS and Linkcell ..................................................... 7
Figure 2-3 Schematic Diagram for Inter-BSC Handoff ........................................................ 11
Figure 2-4 Relationship Between the Four Types of Neighbor Lists ................................... 12
Figure 2-5 Relationship Between NLCSs and Global NLs .................................................. 13
Figure 3-1 A Theoretical Model for Manual Planning .......................................................... 17
Figure 3-2 A Real case of Neighbor Planning..................................................................... 18
Figure 4-1 Subclass Relationship ....................................................................................... 19
Figure 4-2 Intersection Relationship ................................................................................... 20
Figure 4-3 IFHO Relationship Without Common Carriers ................................................... 21
Figure 4-4 Schematic Diagram of an IFHO Area ................................................................ 21
Figure 4-5 IFHO Triggering Flow ........................................................................................ 25
Figure 4-6 Selecting the Target Carrier Sector and Performing Handoff ............................. 26
Figure 4-7 Defining the Critical Sector ................................................................................ 27
Figure 4-8 Defining the Handoff Mode................................................................................ 27
Figure 4-9 Defining the Linkcell .......................................................................................... 28
Figure 4-10 Defining the Candidate Frequency .................................................................. 29
Figure 4-11 Defining the Preferred Neighbor Sectors ......................................................... 30
Figure 4-12 Defining the Threshold Parameters ................................................................. 31
Figure 4-13 Enabling the MAHHO Function ....................................................................... 32
Figure 4-14 One Example for the DAHHO Area ................................................................. 34
Figure 4-15 Coverage Details in the CDT Data .................................................................. 35
Figure 4-16 Applicable Scenario of the Pilot Beacon .......................................................... 37
Figure 4-17 Process of IFHO in Pilot Beacon Mode ........................................................... 40
Figure 4-18 Setting the IFHO Mode of the Carrier Sector to Pilot Beacon .......................... 41
Figure 4-19 Setting NGHBR_CONFIG ............................................................................... 42
Figure 4-20 Setting the Threshold Parameters ................................................................... 42
Figure 4-21 Pilot Beacons Distributed on the BSS Boundary ............................................. 44
Figure 5-1 PilotAdd and PilotCompare ............................................................................... 48
Figure 5-2 Flowchart of the MAHHO in the EVDO System ................................................. 49
Figure 5-3 Interface of Neighbor Carrier List Configuration ................................................ 50
Figure 6-1 BSC Handoff Parameter Table .......................................................................... 52
VII
Internal Use Only
Figure 6-2 Configuration of Global NL of the CDMA 1X System ......................................... 53

Figure 6-3 Information of Global Neighbor List Table ......................................................... 54
Figure 6-4 The Link Cell Tab .............................................................................................. 55
Figure 6-5 Linkcell Configuration Interface ......................................................................... 55
Figure 6-6 NLCS Interface ................................................................................................. 56
Figure 6-7 NLCS Configuration Interface ........................................................................... 56
Figure 6-8 Schematic Diagram of Style 1 ........................................................................... 58
Figure 6-9 Schematic Diagram of Style 2 ........................................................................... 58
Figure 6-10 Setting the IFHO Mode of the nth Carrier of Sector B to Pilot Beacon ............. 59
Figure 6-11 Schematic Diagram of Style 3 ......................................................................... 60
Figure 6-12 Interference on the Boundary of Inter-BSC Hard Handoff................................ 62
Figure 6-13 Carrier F1 Working as a Bridge ....................................................................... 62
Figure 6-14 Configuration Interface of the Global NL of the EVDO System ........................ 64
Figure 6-15 Adding a Foreign Cell to the Global NL in EVDO ............................................ 65
Figure 6-16 Adding the Frequency Information for the Global NL ....................................... 66
Figure 7-1 CDMA 1X Linkcell Configuration Interface ........................................................ 69
Figure 7-2 CDMA 1X NLCS Configuration Interface ........................................................... 70
Figure 7-3 Deleting a Neighbor From the CDMA 1X NLCS Without Handoff Statistics ....... 72
Figure 7-4 Deletion of Bidirectional Neighbor Relations ..................................................... 72
Figure 7-5 Deleting a Neighbor From the CDMA 1X Linkcell Without Handoff Statistics..... 73
Figure 7-6 Starting CDMA 1X Neighbor Optimization With Handoff Statistics .................... 74
Figure 7-7 Parameter Setting of CDMA 1X Neighbor Optimization With Handoff Statistics 76
Figure 7-8 Advanced Settings of CDMA 1X Neighbor Optimization With Handoff Statistics76
Figure 7-9 CDMA 1X Neighbor List Optimization Interface ................................................. 77
Figure 7-10 Scenario That the Same PN Appears in Both the NLHST and RSHST ........... 80
Figure 7-11 Scenario That the Handoff Succeeds Even If the MS Reports That the PN Is in
Its Remaining Set ................................................................................................................. 81
Figure 7-12 Shortcut Menu for Deleting a Neighbor From the NLHST ................................ 82
Figure 7-13 Shortcut Menu for Deleting a Neighbor From the Linkcell................................ 83
Figure 7-14 Opening the EVDO Neighbor Carrier List Configuration Interface ................... 84
Figure 7-15 EVDO Neighbor Carrier List Configuration Interface ....................................... 85
Figure 7-16 EVDO Neighbor Optimization Interface With Handoff Statistics....................... 86
Figure 8-1 Locking a Neighbor ........................................................................................... 87
Figure 8-2 Indicator for a Locked Neighbor ........................................................................ 88
Figure 8-3 Enabling Automatic Neighbor Sequence Sorting ............................................... 89
VIII
Internal Use Only
Figure 8-4 Setting Automatic Neighbor Sequence Sorting.................................................. 90

Figure 8-5 Shortcut Menu for Sequence Adjustment .......................................................... 90
TABLES
Table 2-1 Linkcell Table (Simplified)..................................................................................... 8
Table 2-2 NLCS Table (Simplified) ....................................................................................... 9
Table 2-3 Candidate Frequency Table (Simplified)............................................................. 10
Table 2-4 Preferred Neighbor List Table (Simplified) .......................................................... 10
Table 2-5 Global NL Table (Simplified)............................................................................... 11
Table 2-6 Global Neighbor Sectors Frequency Table (Simplified) ..................................... 11
Table 2-7 NLCS in an EVDO System (Simplified) .............................................................. 14
Table 2-8 Global NL in an EVDO System (Simplified) ........................................................ 15
Table 2-9 Channel Information of Every Global Neighbor Sector in an EVDO System
(Simplified) ........................................................................................................................... 15
Table 4-1 Expected Pilot Beacon Strength When the Threshold Is 2.5 dB ......................... 45
IX
Overview
1.1
Objectives
Internal Use Only
Neighbor configuration is a key part of data configuration because the quality of neighbor
planning and optimization will affect network performance directly. Actually, neighbor
relations are very complex. Every sector may have handoff with more than 20 neighbors
and these neighbors may be of different types.
This document aims at guiding the CDMA RF engineers in planning and optimizing
neighbor lists and it has the following objectives:
1.2
1.3
1.
To introduce some basic concepts about neighbors in ZTEs CDMA radio systems
2.
To guide the RF engineers in planning neighbors of new sites
3.
To guide the RF engineers in configuring and optimizing neighbors
Scope
1.
In this document, only neighbors of CDMA 1X and EVDO systems are discussed,
and other systems (for example, LTE or WiMAX) are not involved.
2.
This document focuses on the planning and optimization of neighbor lists based on
CDT data and the data on the NetNumen. Analysis on drive test data is not included
in this document.
Acronyms
BSC
Base Station Controller
BSS
Base Station Subsystem
BTS
Base Transceiver System
CDT
Call Detail Trace
CFSREQ
Candidate Frequency Search Request
CI
Cell Identity
CS
Carrier Sector
DAHHO
Database Assistance Hard Handoff
GIS
Geographic Information System
GNCELLID
Global Neighbor Cell Identity
GUI
Graphical User Interface
HO
Handoff
IBBE
Interface of BSC and BSC by Ethernet
IBHH
Inter-BSC Hard Handoff
IFHO
Inter-Frequency Handoff
LAC
Local Area Code
LHST
Neighbor List Handoff Statistic Table
MS
Mobile Station
MAHHO
Mobile Assistance Hard Handoff
NCP
Neighbor Cell Planning
NL
Neighbor List
NLCS
Neighbor List for Carrier Sector
NLIFHO
Neighbor List for IFHO
OFS
Other Frequency Search
PN
Pilot Number
PPMRO
Periodical Pilot Measurement Report Order
PSMM
Pilot Strength Measurement Message
RDT
Round Trip Delay
RF
Radio Frequency
RSHST
Remaining Set Handoff Statistic Table
RU
Route Update
SOWD
Serving One-Way-Delay
Internal Use Only
TOWD
1.4
Internal Use Only
Target One-Way-Delay
Technical Support
For support or clarification on information in this guide, email ZTEs CDMA RF
Technologies at NPO@zte.com.cn.
Basic Concepts
2.1
CDMA 1X System
Internal Use Only
ZTEs CDMA 1X systems involve the following four types of neighbor lists:
1.
Linkcell for sector.
2.
Neighbor list for carrier sector, which is called NLCS.
3.
Neighbor list for inter-frequency handoff (only for DAHHO and MAHHO scenarios),
which is called NLIFHO.
4.
Neighbor list for inter-BSC handoff, which is called Global NL.
The above four neighbor lists are independent but interrelated, and their relationship is
described in Section 2.1.1 to 2.1.5.
As shown in Figure 2-1, one BSC may control many BTSs, one BTS may contain several
sectors, and one sector may contain several carriers.
Figure 2-1
Internal Use Only
Hierarchical Network Structure
BSC
BTS X
Sector A
Carrier Sector 1
Carrier Sector 2
Carrier Sector 3
Sector B
Carrier Sector 1
Carrier Sector 2
Carrier Sector 3
Sector C
Carrier Sector 1
Carrier Sector 2
Carrier Sector 3
2.1.1
Linkcell
The linkcell is designed at sector level.
Every sector has its own linkcell. This linkcell defines which sectors may have handoff
with this sector (source sector). A linkcell may include several neighbor sectors. Because
it will not be sent to the MS by the BSS, the number of neighbor sectors in a linkcell is not
limited.
The NLCS must be a subset of linkcell, which means that:
1.
Only after a neighbor sector becomes a member of the linkcell of the source sector
can its carrier sector be a member of the NLCS.
2.
A neighbor sector may be a member of the linkcell but its carrier sector may not be a
member of the NLCS.
2.1.2
Internal Use Only
NLCS
The NLCS is designed at carrier sector level.
Every carrier sector has its own NLCS. The NLCS is a subset of linkcell and it will be sent
to the MS by the BSS on the air link, so there is a limit to the maximum number of
neighbors in an NLCS. According to the CDMA protocol, at most 40 neighbors can be
configured.
The main feature of ZTEs CDMA systems is that every carrier sector can be configured
with at most 20 neighbors. This takes account of the fact that configuring too many
neighbors will increase the time for the MSs to search their neighbor sets. However, if an
MS is in soft handoff status, the maximum number can be 40.
The MS will update its neighbor set after receiving the neighbor list information on the air
link, and then it will search for PNs in its neighbor set and remaining set. The NLCS
decides which PNs will be searched for by the MS.
Figure 2-2 can help understand the function of linkcells.
The red arrow means a source sector, the blue arrows mean neighbor sectors in the
NLCS, and the orange arrows mean neighbor sectors in the linkcell but not in the NLCS.
If one PN is not in the active set, candidate set, or neighbor set, it must be in the
remaining set. For example, if there is one sector (R1) using PN 3 (that is, PN = 3) and
this sector is not in the NLCS, PN 3 must be in the remaining set of the MS.
The MS will search the remaining set to find a strong pilot in this case, PN 3 and
then report the phase and strength of this pilot to the BSS through a PILOT STRENGTH
MEASUREMENT message (PSMM). After the BSS confirms that this pilot is PN 3, it will
try to find PN 3 in the linkcell. If the linkcell includes one sector using PN 3, the BSS will
be able to identify the target sector accurately; if the linkcell does not include one sector
using PN 3, the BSS will be unable to identify the target sector because PN 3 is reused
by more than one sector.
Figure 2-2
Internal Use Only
Schematic Diagram for an NLCS and Linkcell
Sector = R1
PN = 3
MS
Source
Sector
Table 2-1 shows that the linkcell of BTS4s alpha sector has 27 neighbor sectors and
Table 2-2 shows the contents of the neighbor list of BTS4-Alpha Sector-Carrier 0 and
BTS4-Alpha Sector-Carrier 1. It can be found that Table 2-2 is a subset of Table 2-1.
Table 2-1
Internal Use Only
Linkcell Table (Simplified)
NCELL
SWITCH
BTSNO CELL PILOT_PN SYSTEM CI
NCELL GNCELLID MARKETID NUMBER
4
0
15
107
482
0
1
4
4
0
57
147
157
0
1
4
4
0
75
32
493
0
1
4
4
0
93
23
577
0
1
4
4
0
105
10
571
0
1
4
4
0
114
58
439
0
1
4
4
0
123
11
502
0
1
4
4
0
144
94
550
0
1
4
4
0
153
22
591
0
1
4
4
0
171
16
569
1
1
4
4
0
180
1 40002
1
1
4
4
0
183
107
483
1
1
4
4
0
189
85
464
1
1
4
4
0
243
32
494
1
1
4
4
0
273
10
572
1
1
4
4
0
303
4
560
1
1
4
4
0
312
94
551
1
1
4
4
0
321
5
404
1
1
4
4
0
339
6
501
2
1
4
4
0
348
1 40003
2
1
4
4
0
351
107
484
2
1
4
4
0
411
32
495
2
1
4
4
0
441
10
573
2
1
4
4
0
459
11
504
2
1
4
4
0
462
2
564
2
1
4
4
0
471
4
561
2
1
4
4
0
480
94
552
2
1
4
Table 2-2
Internal Use Only
NLCS Table (Simplified)
NCELL
BTSNO CELL CARRIER PILOT_PN SYSTEM NCELL GNCELLID CI
4
0
0
105
10
0
571
4
0
0
273
10
1
572
4
0
0
171
16
1
569
4
0
0
153
22
0
591
4
0
0
93
23
0
577
4
0
0
75
32
0
493
4
0
0
243
32
1
494
4
0
0
411
32
2
495
4
0
0
114
58
0
439
4
0
0
15
107
0
482
4
0
0
351
107
2
484
4
0
1
462
2
2
564
4
0
1
303
4
1
560
4
0
1
471
4
2
561
4
0
1
339
6
2
501
4
0
1
105
10
0
571
4
0
1
273
10
1
572
4
0
1
441
10
2
573
4
0
1
123
11
0
502
4
0
1
459
11
2
504
4
0
1
171
16
1
569
4
0
1
153
22
0
591
4
0
1
75
32
0
493
4
0
1
243
32
1
494
4
0
1
411
32
2
495
4
0
1
114
58
0
439
4
0
1
144
94
0
550
4
0
1
312
94
1
551
4
0
1
480
94
2
552
4
0
1
351
107
2
484
4
0
1
57
147
0
157
2.1.3
NLIFHO
There are the following three types of inter-frequency handoff in CDMA 1X systems:
DAHHO
MAHHO
Inter-frequency handoff in pilot beacon mode
If only inter-frequency handoff in pilot beacon mode is available, the NLIFHO can be
ignored; if DAHHO or MAHHO is available, the NLIFHO will be used.
Internal Use Only
The NLIFHO is designed at sector level. Every NLIFHO contains two types of tables: One
is the Candidate Frequency table, and another is the Preferred Neighbor List table. The
Candidate Frequency table defines the target frequencies of IFHO. Every target
frequency has one Preferred Neighbor List table, which defines the target neighbors of
IFHO at this frequency.
For example, Table 2-3 shows that BTS2s alpha sector has one target frequency for
IFHO: It is Channel 283 (CDMA_FREQ = 283) and its carrier ID (NCARRIER) is 0. Table
2-4 shows that there are two preferred neighbors for IFHO in Channel 283 and these two
preferred neighbors are BTS1s beta sector (CI = 40002) and BTS5s beta sector (CI =
404).
Table 2-3
Candidate Frequency Table (Simplified)
BTSNO
CELL
2
Table 2-4
BAND_CLASS
CDMA_FREQ NCARRIER USE_TIMING COUNT
0
283
0
0
2
Preferred Neighbor List Table (Simplified)
ISPREF
BTSNO CELL PILOT_PN NEIGHBOR
2
2
0
0
180
321
NCELL
NCARRIER SYSTEM NCELL CI
1
1
0
0
1
5
1 40002
1
404
When DAHHO or MAHHO is triggered, the BSS will judge which candidate frequency
should be selected according to the algorithm if there is more than one candidate
frequency in the Candidate Frequency table and then judge which neighbor is the target
of IFHO from the Preferred Neighbor List table.
2.1.4
Global NL
Inter-BSC handoff may happen near BSC boundaries. If the BSCs are all provided by
ZTE and are connected to each other in IBBE mode, the inter-BSC handoff may be soft
handoff. If the BSCs are provided by different vendors or are not connected in IBBE
mode even if they are all provided by ZTE, the inter-BSC handoff will be hard handoff.
The global NL should be configured no matter which type of inter-BSC handoff is
selected.
Every global NL contains two tables. One table defines which sectors of other BSCs may
have handoff with sectors of the source BSC; another table lists the channels of these
neighbor sectors.
For example, Table 2-5 shows that one sector of another BSC is configured as a global
neighbor sector of the source BSC. The parameters of this sector are as follows:
10
Internal Use Only
CI = 1321, PILOT_PN = 12, and GNCELLID = 0

Table 2-6 shows that this global neighbor sector (GNCELLID = 0) has one channel
whose parameter values are as follows:
BAND_CLASS = 0 (800M) and CDMA_FREQ = 283
Table 2-5
Global NL Table (Simplified)
GNCELLID ALIAS_B
CI_DISCRI
GNCELLTYPE
MINATOR CI
0 Dabieshan
Table 2-6
SRCH_
SWITCH
PILOT_PN PILOT_INC WIN_N MARKETID NUMBER
1321
12
Global Neighbor Sectors Frequency Table (Simplified)
GNCELLID GNCARRIERID BAND_CLASS CDMA_FREQ PAGE_NUM UCISBEACON

0
0
0
283
1
0
Figure 2-3 shows how a global NL works. For example, an MS is in active state on the
BSC boundary. It detects a strong pilot (PN 6) and is going to perform a handoff.
Although the MS does not know whether PN 6 is inter-BSC or not, it can search for PNs
and report their phases to the BSS. The BSS needs to know this information to make
handoff judgments. The correct neighbor configuration procedure is:
1.
Configure Sector B of Target BSC in the global NL of Source BSC.
2.
Configure this global neighbor sector in the linkcell of Sector A.
3.
Configure this global neighbor sector in the NLCS of Sector As carrier sector.
Figure 2-3
Schematic Diagram for Inter-BSC Handoff
BSC
Boundary
Source BSC
Sector A
PN = 3
Target BSC
Sector B
PN = 6
MS
11
2.1.5
Internal Use Only
Relationship Between the Above Four Types of Neighbor Lists

Figure 2-4 shows the relationship between the above four types of neighbor lists. The
NLCS and NLIFHO are subsets of the linkcell. If a neighbor sector is of another BSC, it
should be configured in the global NL of the source BSC first and then be configured in
the linkcell of the source sector. If necessary, it can also be configured in the NLCS or
NLIFHO.
Figure 2-4
Relationship Between the Four Types of Neighbor Lists
Linkcell of One Sector

NLCS for This
Sectors Carrier 1
NLCS for This

Sectors Carrier 2
Global NL
NLIFHO
2.2
Information of Sectors of
Other BSCs
EVDO System
ZTEs EVDO systems involve the following two types of neighbor lists: NLCS and
global NL. Compared with CDMA 1X systems, ZTEs EVDO systems do not involve the
following two types of neighbor lists: NLIFHO and linkcell.
In an EVDO system, one NLCS may include frequency information and the MS can
search for PNs of other frequencies in active state, so IFHO will become easier and
simpler.
Figure 2-5 shows the relationship between NLCSs and global NLs:
1.
The NLCS of the source sectors Carrier 1 is independent from that of the source
sectors Carrier 2. They can be identical, intersecting, or disjoint sets.
2.
If sectors of other BSCs have been defined in the global NL of the source sector,
they can be used and configured in its NLCSs.
12
Figure 2-5
Internal Use Only
Relationship Between NLCSs and Global NLs
NLCS of the Source

Sectors Carrier 2
Global NL
Information of Sectors of
Other BSCs
NLCS of the Source

Sectors Carrier 1
2.2.1
NLCS
The NLCS is designed at carrier sector level.
Every carrier sector has its own NLCS. This NLCS may contain neighbor carrier sectors
that use the same channel with the source carrier sector and neighbor carrier sectors that
use different channels, so an NLCS may include two or more neighbors using the same
PN but different channels. This is a big difference between the NLCS of a CDMA 1X
system and that of an EVDO system. Usually, it is prohibited to configure two co-PN
neighbors in the same NLCS.
If the NLCS contains neighbor carrier sectors of other channels, the EVDO MS will
search for specified PNs of other channels periodically in active state, so IFHO will
become easier.
The NLCS of the EVDO system will also be sent to the MS on the air link, so there is a
limit to the maximum number of neighbors in an NLCS too. According to the EVDO
protocol, at most 31 neighbors can be configured.
Table 2-7 shows that Carrier-Sector71-0-1 (BTS71-Alpha Sector-Carrier 1) has six
neighbor carrier sectors. These six neighbors are from the same channel because their
NBCARRIERID parameter values are all 1.
13
Table 2-7
Internal Use Only
NLCS in an EVDO System (Simplified)
NBCAR
ANID SYSTEM CELLID CARRIERID NBANID NBSYSTEM NBCELLID RIERID PILOTPN
0
71
0
1
0
111
1
1
216
0
71
0
1
0
71
2
1
208
0
71
0
1
0
71
1
1
204
0
71
0
1
0
106
0
1
248
0
71
0
1
0
106
1
1
252
0
71
0
1
0
106
2
1
256
0
71
1
1
0
71
0
1
200
0
71
1
1
0
111
1
1
216
0
71
1
1
0
71
2
1
208
0
71
1
1
0
106
0
1
248
0
71
1
1
0
106
1
1
252
0
71
1
1
0
106
2
1
256
0
71
2
1
0
71
0
1
200
0
71
2
1
0
71
1
1
204
0
71
2
1
0
111
1
1
216
0
71
2
1
0
106
0
1
248
0
71
2
1
0
106
1
1
252
0
71
2
1
0
106
2
1
256
2.2.2
Global NL
The function of global NL in an EVDO system is the same as that in a CDMA 1X system.
To enable inter-BSC handoff, the RF engineers should define carrier sectors of other
BSCs in the global NL of the source BSC. Otherwise, the BSS cannot identify the correct
carrier sectors according to the phases reported by the MS.
Similarly, every global NL in the EVDO system also has two tables. One table defines
which sectors of other BSCs may have handoff with sectors of the source BSC; another
table lists the channels of these neighbor sectors.
Table 2-8 lists some sectors of other BSCs that are configured as global neighbors of the
source BSC, including the values of their GNCELLID, NBANID, Pilot PN, Band Class,
Color Code, CI, NBSYSTEM, and NBCELLID parameters.
14
Table 2-8
Internal Use Only
Global NL in an EVDO System (Simplified)
ANID GNCELLID NBANID Pilot PN Alias_b

0
0
1
126 YZ_BSC3_404_0
0
2
1
462 YZ_BSC3_404_2
0
3
1
42 YZ_BSC3_410_0
0
4
1
210 YZ_BSC3_410_1
0
5
1
378 YZ_BSC3_410_2
0
6
1
12 YZ_BSC3_468_0
0
7
1
180 YZ_BSC3_468_1
0
8
1
348 YZ_BSC3_468_2
0
9
0
63 YZ_BSC4_308_0
0
10
0
231 YZ_BSC4_308_1
Band Color
Class Code
0
0
0
0
0
0
0
0
0
0
CI
NBSYSTEM NBCELLID
103424
404
0
103426
404
2
104960
410
0
104961
410
1
104962
410
2
119808
468
0
119809
468
1
119810
468
2
78848
308
0
78849
308
1
Table 2-9 shows the channel information of every global neighbor sector. In this example,
the channel numbers are all 37.
Table 2-9 Channel Information of Every Global Neighbor Sector in an EVDO System
(Simplified)
Channel
ANID GNCELLID GNCARRIERID SYSTEMTYPE BCSUBNET Number NBCARRIERID
0
0
0
0
255
37
3
0
2
0
0
255
37
3
0
3
0
0
255
37
3
0
4
0
0
255
37
3
0
5
0
0
255
37
3
0
6
0
0
255
37
3
0
7
0
0
255
37
3
0
8
0
0
255
37
3
0
9
0
0
255
37
3
0
10
0
0
255
37
3
15
Internal Use Only
Principles for Neighbor Planning

This chapter comprises two parts. The first part introduces the basic principles for
neighbor planning; the second part gives a theoretical model and one example.
Before adding a new site to an existing network, the RF engineers should properly plan
the neighbors of this new site and modify the neighbor lists of the sectors adjacent to this
new site. Otherwise, handoff from the existing sectors to the new site will fail. Neighbor
list modification for the adjacent sectors is complex because it involves many sectors
neighbor lists and should be based on not only the cellular structure but also the handoff
statistics.
Neighbor planning principles in this chapter are mainly based on soft handoff. For details
about the neighbor planning for IFHO, see Chapter 4.
3.1
Basic Principles
Usually, neighbor planning should follow the basic principles below:
1.
If one sectors coverage area is adjacent to another sectors coverage area, these
two sectors should be configured as bidirectional neighbors.
2.
Excessive neighbor configurations should be avoided. Otherwise, it will take more

time for the MS to search its neighbor set.
3.2
Practice of Neighbor Planning
3.2.1
Theoretical Model
Figure 3-1 shows an ideal cellular structure of the radio network. The directions of arrows
mean the bearing of antennas. If the RF engineers want to plan the neighbors of the
sector that uses PN 4 (the source sector, with a red real-line arrow), they can take the
following steps:
1.
Add all the other sectors of this site to the neighbor list, except for remote sectors.
2.
Identify the first innermost circle of adjacent sectors (with purple arrows) and the
second innermost circle of adjacent sectors (with blue arrows).
3.
Set the sectors of the first innermost circle and the second innermost circle that are
in the forward direction (from BTS to MS) of the source sector as the neighbors.
16
4.
Internal Use Only
Set the sectors of the first innermost circle in the reverse direction (from MS to BTS)
of the source sector as the neighbors.
According to the above steps, the following sectors should be set as neighbors:
1.
Softer-handoff sectors: PN 172 and PN 340
2.
Adjacent sectors of the first innermost circle: PN 108, PN 44, PN 20, PN 252, PN 84,
PN 404, PN 68, PN 236, PN 100, and PN 436
3.
Adjacent sectors of the second innermost circle: PN 292, PN 196, PN 468, PN 132,
PN 300, PN 372, and PN 486
All the neighbors are marked with dotted-line arrows, as shown in Figure 3-1.
A Theoretical Model for Manual Planning
148
36
22
31
22
52
100
140
20
124
68
42
12
4
108
26
60
84
44
92
0
0
76
39
44
18
38
41
34
116
6
27
47
35
46
45
8
34
26
22
17
38
42
4
21
43
4
0
40
23
20
48
36
28
25
30
37
18
29
19
46
28
132
Figure 3-1
30
17
3.2.2
Internal Use Only
Real Case
The theoretical model in Section 3.2.1 is based on an ideal topological structure. Real
networks may have different structures, but the principles are similar.
Figure 3-2 demonstrates a real case of neighbor planning for one sector.
The red sector is the source sector and the green sectors are the neighbors. It can be
found that most neighbors are distributed in the forward direction of the source sector.
Figure 3-2
A Real case of Neighbor Planning
18
Internal Use Only
Neighbors for IFHO (CDMA 1X)

There are three types of IFHO: DAHHO, MAHHO, and handoff in pilot beacon mode. The
processes and principles of DAHHO and MAHHO are a little similar. Hence DAHHO and
MAHHO are described in the same section.
4.1
DAHHO and MAHHO
4.1.1
Applicable Scenarios
IFHO can be applied in the following scenarios.
4.1.1.1
Two Sites With Common Carriers

Two sites have different carrier configurations but they have common carriers. This
scenario can be seen into two cases.
1.
Subclass relationship
Subclass relationship means that one sites carrier configuration is a subclass of
another sites carrier configuration.
For example, one sites carrier configuration is C1/C2/C3//Cn and another sites
carrier configuration is C1/C2/C3, as shown in Figure 4-1.
Figure 4-1
Subclass Relationship
Cn
C4
C3
C2
C1
Site A
C3
C2
C1
Red Line means IFHO.

Blue Line means soft HO.
Site B
19
Internal Use Only
In this case, C1, C2, and C3 are common carriers of Site A and Site B, and the
carrier configuration of Site B is a subclass of the carrier configuration of Site A.
As shown in Figure 4-1, the MS working on C1, C2, or C3 will perform soft handoff
and only the MS working on C4, , or Cn of Site A will perform inter-frequency hard
handoff if this handoff is necessary. The target carrier of IFHO will be one of the
common carriers.
2.
Intersection relationship
Intersection relationship means that two sites have common carriers but the rest
carriers of these two sites are different.
For example, one sites carrier configuration is C1/C2/C3/./Cn and another
sites carrier configuration is C1/C2/C3/Cn+1/Cn+2/./Cm, as shown in Figure
4-2.
Figure 4-2
Intersection Relationship
Cn
Cm
C4
Cn+1
C3
C2
C1
Site A
C3
C2
C1

Site B
In this case, C1, C2, and C3 are common carriers of Site A and Site B, which means
that they are an intersection of Site A and Site B.
As shown in Figure 4-2, the MS working on C1, C2, or C3 will perform soft handoff
and the MS working on C4, ., or Cn of Site A or Cn+1, , or Cm of Site B will
perform inter-frequency hard handoff if this handoff is necessary. The target carrier
of IFHO will be one of the common carriers.
4.1.1.2
Two Sites Without Common Carriers

Two sites have different carrier configurations and they have no common carriers.
20
Internal Use Only
For example, one sites carrier configuration is C1/C2/C3 and another sites carrier
configuration is C4/C5/C6, as shown in Figure 4-3.
Figure 4-3
IFHO Relationship Without Common Carriers
C3
C2
C1
C6
C5
C4
Site A

Site B
In this case, there will be no soft handoff and only IFHO may happen. The target carrier
will be one carrier of the other site.
4.1.2
Triggering Conditions
4.1.2.1
IFHO Area
When an MS moves to the coverage edge of a carrier sector, if the following two
conditions are satisfied, this area can be defined as an IFHO area.
1.
Signals from the current carrier sector are weak and the MS cannot find or lock
other PNs on same channel from other sectors.
2.
There are strong signals on other channels from other sectors in this area.
Figure 4-4 shows an IFHO area. Sector 1 and Sector 2 have a common carrier (Carrier 1).
If the MS moves into the IFHO area, where signals of Carrier 2 are weak and signals of
Carrier 1 are strong, IFHO will occur.
Figure 4-4
Schematic Diagram of an IFHO Area

IFHO Area
Coverage of
Sector 1-Carrier 2
Coverage of
Sector 2-Carrier 1
Coverage of
Sector 1-Carrier 1
21
Internal Use Only
The RF engineers can set a carrier sector as a critical sector in the Carrier_Para table.
Once the active set of the MS in conversation is changed, the BSS will judge whether all
the active PNs are from critical sectors. If they are all from critical sectors, IFHO will be in
available state and the BSS will send PPMRO messages to the MS to ask for information
about the radio environment periodically. Then the BSS will decide whether to initiate
IFHO according to the MS-reported information.
In the case as shown in Figure 4-4, Sector 1-Carrier 2 should be set as a critical sector.
4.1.2.2
Threshold Parameter Setting

There are four thresholds for IFHO as follows:
1.
RTD_Threshold_Voice: RTD threshold for voice service
2.
T_DROP_SSHO_Voice: pilot strength threshold for voice service
3.
RTD_Threshold_Data: RTD threshold for data service
4.
T_DROP_SSHO_Data: pilot strength threshold for data service
These four parameters are on the Carrier Parameter tab and can be modified on the
NetNumen.
Units, default values, and ranges of these parameters are as follow:
1.
RTD_Threshold_Voice and RTD_Threshold_Data
Unit: 1/8 chip
Default value: 0
Range: 0~32767
Note:
It is more difficult to trigger IFHO with a greater value and easier to trigger IFHO with
a smaller value.
2.
T_DROP_SSHO_Voice and T_DROP_SSHO_Data
Unit: 0.5 dB
Default value: 24
Range: 0~63
22
Internal Use Only
Note:
It is more difficult to trigger IFHO with a greater value and easier to trigger IFHO with
a smaller value. Because the unit is negative, a greater value means smaller pilot
strength and a smaller value means greater pilot strength.
4.1.2.3
Processes of DAHHO and MAHHO

The MS will send PSMMs periodically in the IFHO area upon request from the BSS.
However, IFHO rarely happens in most part of this area, especially under the following
three circumstances:
Signals of this carrier are not weak enough.
Some PNs in the active set are not from critical sectors.
The distance between the MS and BTS is too short.
Only when all the following three conditions are satisfied can IFHO be triggered:
All the PNs in the active set are from critical sectors.
Strength of all the PNs in the active set is smaller than the relevant
T_DROP_SSHO_Voice or T_DROP_SSHO_Data parameter value in the PSMM.
RDTs measured on the reverse link are all greater than the relevant
RTD_Threshold_Voice or RTD_Threshold_Data parameter value.
If all the above three conditions are satisfied, the BSS will initiate IFHO.
1.
DAHHO mode
i.
The BSS selects the carrier with the lightest load from the Candidate
Frequency table as the target carrier of IFHO.
ii.
In this mode, the BSS cannot get detailed coverage information of the target
band class and it will decide target sectors according to the Preferred Neighbor
List table.
iii.
Then the BSS allocates resources of these target sectors for the MS. After the
resource allocation is completed, the BSS will send information about the
resources to the MS through a HANDOFF DIRECTION message.
iv.
The MS seizes the traffic channel according to the HANDOFF DIRECTION

message and sends a HANDOFF COMPLETION message to the BSS after
the seizure is completed.
23
2.
4.1.2.4
Internal Use Only
MAHHO mode
i.
The BSS selects the carrier with the lightest load from the Candidate
Frequency table as the target carrier of IFHO.
ii.
In this mode, the BSS will send a CFSREQ message to the MS once the BSS
starts the IFHO process. Then the MS will search for PNs of the target carrier
sectors and report the details according to the CFSREQ message.
iii.
The BSS arrays all the MS-reported PNs according to their pilot strength and
then selects the top N strongest PNs as the target carrier sectors. N depends
on the maximum leg number in the active set (Leg number = Number of PNs).
iv.
Then the BSS allocates the resources of these target sectors for the MS. After
the resource allocation is completed, the BSS will send information about the
resources to the MS through a HANDOFF DIRECTION message.
v.
The MS seizes the traffic channel according to the HANDOFF DIRECTION

message and send a HANDOFF COMPLETION message to the BSS after the
seizure is completed.
Flowcharts
1.
Trigger IFHO.
24
Figure 4-5
Internal Use Only
IFHO Triggering Flow
The MS is in conversation or
data service.
The MS sends PSMMs

periodically.
No
Are all the PNs in the active
set from critical sectors?
Yes
No
Is the strength of all the

PNs in the active set
smaller than
T_DROP_SSHO?
Yes
The BSS asks the MS to

send PSMMs periodically.
Are the RTDs of all the PNs
in the active set greater
than RTD_Threshold?
No
Yes
Does the MS support two

band classes?
No
Yes
IFHO between band
classes starts.
2.
Select the target carrier sector and perform handoff.
25
Figure 4-6
Internal Use Only
Selecting the Target Carrier Sector and Performing Handoff

Note:
HDM: Handoff Direction Message
HCM: Handoff Completion Message
TCH: Traffic Channel
IFHO has been

triggered.
Is it in DAHHO
mode?
No
MAHHO mode
Yes
The BSS queries the
Candidate Frequency table.
The BSS queries the

Candidate Frequency table.
The BSS selects the lightestload carrier as the target

carrier of IFHO.
The BSS selects the lightestload carrier as the target

carrier of IFHO.
The BSS arranges resources in the

preferred neighbor carrier sectors of the
target carrier according to the Preferred
Neighbor List table.
The BSS sends a CFSREQ message

to the MS to ask it to search the IFHO
neighbor list of the target carrier.
Are the resources

available?
The IFHO neighbor list is defined in the Preferred

Neighbor List Table.
No
The MS reports candidate

frequency information.
Yes
The BSS arrays PNs
according to the pilot
strength and selects Top N.
The BSS informs the MS

through an HDM.
N depends on the maximum leg

number in the active set.
The MS seizes the TCH

and replies with an HCM.
Yes
Neighbor lists and other
system parameters are
updated.
Is the strength of Top N

PNs strong enough?
No
IFHO has finished.
4.1.3
Configuration Steps
4.1.3.1
DAHHO Mode
1.
IFHO has
failed.
IFHO Is
terminated.
Define the critical sector.

If the carrier sector is defined as critical sector, every MS in this carrier sector will
report the PSMM periodically; otherwise the BSS cannot know the radio
environment of the MS. This parameter can be set to Yes or No in the Carrier
Parameters tag.
26
Figure 4-7
2.
Internal Use Only
Defining the Critical Sector
Define the handoff mode.

On the Cell Parameters tab, the parameter Handoff mode can be set to
HandDown or HandOver. If the active set after the IFHO does not contain any
source sector and only has the preferred neighbor sectors, this parameter should be
set to HandOver. If the active set after the IFHO also contains source sectors, this
parameter should be set to HandDown.
In the scenario described in Section 4.1.1.1, this parameter value is suggested to be
HandDown; in the scenario described in Section 4.1.1.2, this parameter should be
set to HandOver.
Figure 4-8
3.
Defining the Handoff Mode
Configure the linkcell.

In the sector-level node of configuration management function in the NetNumen,
you can add target sectors on the Link Cell tab.
27
Figure 4-9
4.
Internal Use Only
Defining the Linkcell
Configure the candidate frequency.

The meaning of the candidate frequency is described as follows. When the IFHO
happens, the BSS will indicate the MS to hand off to the candidate frequency. If you
do not define this candidate frequency, the BSS cannot identify the target carrier.
In the sector-level node of the configuration management function in the NetNumen,
you can add target carriers on the Neighbor Frequency tab.
In the scenario described in Section 4.1.1.1, the candidate frequency is for common
carriers.
In the scenario described in Section 4.1.1.2, the candidate frequency is for carriers
of the other site.
28
Figure 4-10
5.
Internal Use Only
Defining the Candidate Frequency
Configure the preferred neighbor sectors.

After the candidate frequency configuration is completed, you should configure the
preferred neighbor sectors of this candidate frequency, so that the BSS can indicate
the MS to hand off to the preferred neighbor sector of the candidate frequency when
the IFHO happens.
At most 20 neighbor sectors can be set for every candidate carrier but not all the
neighbor sectors are preferred neighbor sectors. Only the neighbor sectors marked
with preferred neighbor cell are preferred neighbor sectors; other neighbor sectors
are available in MAHHO mode.
Note:
The maximum number of preferred neighbor sectors depends on the maximum
number of legs in the active set. Suppose the maximum number of legs in the active
set is N. If the parameter Handoff mode is set to HandDown, the maximum number
of preferred neighbor sectors will be N-1; if the parameter Handoff mode is set to
HandOver, the maximum number of preferred neighbor sectors will be N.
29
Figure 4-11
6.
Internal Use Only
Defining the Preferred Neighbor Sectors
Configure the threshold parameters.

In Section 4.1.2.2, four thresholds are introduced. The four thresholds are set as
shown in the following figure.
30
Figure 4-12
4.1.3.2
Internal Use Only
Defining the Threshold Parameters
MAHHO Mode
1.
Enable the MAHHO function.

Generally, the MAHHO function is disabled, so the RF engineers should enable this
function first.
Under the BSS-level node, the parameter MS whose version is more than 6
supports MAHHO should be set to Support on the Switch Parameters tab. As per
the protocol, the IS95 mobile cannot support the MAHHO mode. Therefore,
regarding the IS95 mobile, the BSS will enable the DAHHO mode no matter the
MAHHO mode is enabled or not.
31
Figure 4-13
2.
Internal Use Only
Enabling the MAHHO Function
Define the critical sector.

This step is the same as Step 1 in Section 4.1.3.1.
3.
Configure the handoff mode.

Actually, this step is unnecessary for MAHHO mode. However, if a few IS-95 users
are still in service, DAHHO mode should also be enabled. Therefore this step
cannot be ignored.
4.

5.
Configure the candidate frequency.

6.
Configure the neighbor sector of the candidate frequency.

After the candidate frequency configuration is completed, the RF engineers should
configure the neighbor sector of this candidate frequency, so that the BSS can
indicate the MS to search the PNs on the candidate frequency when the IFHO
happens in MAHHO mode. This step is the same as Step 5 in Section 4.1.3.1.
32
Internal Use Only
At most twenty neighbor sectors can be set for every candidate carrier. The BSS will
send the information about these neighbor sectors to the MS without considering
whether they are preferred neighbor sectors or not.
Because MAHHO mode is only available for the MS in the CDMA 1X system, the
BSS will deal with the IFHO of the IS95 mobile in DAHHO mode. Then if few IS95
mobiles are still in service, though the MAHHO has been enabled, the preferred
neighbor sectors are taken into account.
7.
Configure the threshold parameters.

4.1.4
NLIFHO (DAHHO) Planning and Optimization

The maximum number of NLIFHOs is mentioned in Section 4.1.3. Actually the preferred
neighbor sectors are few. If the maximum number of legs in the active set is set to 4, the
number of preferred neighbor sectors can be 3 in the handdown mode and 4 in the
handover mode.
Because the NLIFHO is correlative to the trigger threshold and coverage, NLIFHO
planning and optimization are not easy, though the neighbor sectors are few.
Figure 4-14 shows an example for DAHHO mode. The brown sectors all have three
rd
carriers and green sectors all have two carriers. In order to avoid the call drops on the 3
rd
carrier, the 3 carriers of red sectors are planned to be critical cells. These critical cells all
rd
have three carriers and the MS can work on their 3 carriers. Now their NLIFHOs should
be planned as the direct targets of the IFHO.
Take the NLIFHO of PN 207 as an example. If the triggering conditions are defined
strictly, the IFHO may happen in the area far away from the source sector (PN 207).
Therefore the Preferred Neighbor List table should contain PN 102, PN 57, and PN 258.
If the triggering conditions are not strict, the IFHO will happen in the area near the source
sector (PN 207) and the Preferred Neighbor List table should contain PN 426, PN 90, and
PN 258.
rd
Similarly, even if the triggering conditions are defined, the coverage of the 3 carrier of
the source sector (PN 207) will influence the inter-frequency handoff area. If the transmit
power and channel gain are large, the signal will not be weak until the MS is far away
from the source sector. If the transmit power and channel gain are small, the signal will
be weak when the MS is still near the source sector. The NLIFHOs of the above two
cases will be different definitely.
33
Figure 4-14
Internal Use Only
One Example for the DAHHO Area
According to the above analysis, planning and optimization rules can be summarized as
follows.
1.
The coverage of the critical cell is very important. If the coverage details are clear,
the IFHO area can be planned and the correlative NLIFHO, trigger threshold,
transmit power, and channel gain can be confirmed.
2.
Coverage details can be the drive test result, simulation result, or CDT data.
i.
There are few details about the drive test result, so the DAHHO mode is only
applied in rural area with few roads.
ii.
Simulation result is very useful but the high-definition digital map, exact
propagation model, and accurate BTS information is necessary for the
simulation . In addition, the exact locations of real users cannot be simulated.
iii.
The NetMAX can process the CDT data and export and display the actual
users' GIS information. But its shortage is that the location error may be
serious in some cases. Figure 4-15 shows an example and PN 498s IFHO
area is marked with orange line.
34
Figure 4-15
Internal Use Only
Coverage Details in the CDT Data
Generally, the simulation result can be applied to the NLIFHO planning and the CDT
data can be applied to the NLIFHO optimization.
3.
4.1.5
If the RF engineers do not have any coverage detail, the NLIFHO optimization is
mainly based on the handoff statistics and BTS information. For example, if the RF
engineers want to optimize the Preferred Neighbor List table of the source sector
st
nd
(PN 207), they can obtain the handoff statistical information of the 1 carrier and 2
carrier of the source sector and then find which green sector performs handoffs
most frequently with the source sector. These results will be included in the
Preferred Neighbor List table. The contents of this paragraph are applicable to the
scenario in Section 4.1.1.1, not that in Section 4.1.1.2.
NLIFHO (MAHHO) Planning and Optimization

The maximum number of NLIFHOs was mentioned in Section 4.1.3. If the MAHHO mode
is enabled, the maximum number of preferred neighbor sectors is 20. Compared to the
NLIFHO (DAHHO) planning and optimization, the NLIFHO (MAHHO) planning and
optimization are simpler, so more neighbor sectors can be configured.
Regarding the planning in MAHHO mode, the drive test result, simulation result, and CDT
data can be applied so as to get an exact result. If the topology structure of the network is
simple, the principles described in Chapter 3 can be followed.
35
Internal Use Only
Regarding the optimization in MAHHO mode, the following operations are necessary.
1.
2.
4.1.6
Remove the unnecessary neighbor sectors in the NLIFHO. Because twenty

neighbor sectors can be configured in the NLIFHO, sometimes there may be
unnecessary neighbor sectors. This will increase the time that the MS needs to
search for all the PNs in the candidate frequency search request message
(CFSRQM) and then increase the IFHO failure rate.
i.
The RF engineers can get the handoff statistical information of the non-critical
st
nd
cell carriers of the source sector. Take the 1 and 2 carriers of PN 207 in
Figure 4-14 for example. If the number of handoffs is very small, the handoff
between the neighbor sector and source sector happens rarely. Therefore this
unimportant neighbor sector can be deleted if the Preferred Neighbor List table
also contains it.
ii.
Similarly, if one important neighbor sector with many handoffs is found and it
was not in the Preferred Neighbor List, it can be added to the table.
iii.
The contents of this paragraph are applicable to the scenario of Section 4.1.1.1,
not that in Section 4.1.1.2.
The CDT data can be used to help the RF engineers. According to the CDT data
and triggering conditions, the IFHO area can be confirmed and then the RF
engineers can see which non-critical sectors signals can reach this area. At last,
these possible sectors will be configured into the NLIFHO. Actually this is actually in
the planning process.
Inter-Band IFHO
If the IFHO happens between different bands, for example, from 800 MHz to 1.9 GHz,
two switches should be noted.
If these two switches are disabled, the inter-frequency handoff between different bands
does not follow the MAHHO procedure, but follows the DAHHO procedure. In this kind of
scenario, the BSS indicates the MS to perform the inter-frequency handoff directly,
regardless of the strength of neighbor sectors' PNs in the target carrier. In this case, if the
strength is very weak and the inter-frequency handoff fails. Then the MS requests
another inter-frequency handoff and this will cause vicious circle and many
inter-frequency handoff failures.
So it is suggested that these two switches should be enabled. These two switches are
Switch 77 (SWITCH_Querry_MS_Interbandclass_HO_Capability) and Switch 84
(SWITCH_Support_MS_Assist_Bandclass_HO) in the BSS Switch Parameter Table at
BSC level.
If Switch 84 is off, the BSS cannot support the inter-frequency handoff between different
bands in MAHHO mode. Hence the BSS will not indicate the MS to search for the PNs in
36
Internal Use Only
other frequencies in other bands but it will indicate the MS to perform the inter-frequency
handoff between the bands directly.
If Switch 84 is on, the BSS indicates the MS to search for the PNs in the frequencies in
other bands. If the search result is positive, the inter-frequency handoff will be triggered.
Then the unnecessary inter-frequency handoffs are reduced and inter-frequency handoff
failures are avoided.
If Switch 77 is on, the BSS inquires whether the MS supports different bands. Then the
BSS can decide whether the inter-frequency handoff between bands is feasible or not.
4.2
Pilot Beacon
4.2.1
Applicable Scenario
The applicable scenario of the pilot beacon is simple.
In Figure 4-16, there are three sectors. Sector A and Sector B have 3 carriers and Sector
rd
C has only one carrier. The MS is working on the 3 carrier of Sector A during the
conversation and then it moves to Sector C. Because the Sector C has no Carrier 3, the
rd
MS still works on the 3 carrier of Sector B and Sector A though the signal may be weak.
nd
rd
After the IFHO modes of 2 and 3 carriers of Sector B are set to pilot beacon, when the
MS reports the signal strength information of the pilot beacon to the BSS and the strength
is strong enough, the BSS can detect that the MS is near the boundary of a different
carrier and decides to perform the IFHO.
Figure 4-16
Applicable Scenario of the Pilot Beacon
Boundary
Between Carriers
Area of Three Carriers
Pilot Beacon Area
Area of One carrier
3rd Channel
3rd Channel
2nd Channel
2nd Channel
1st Channel
1st Channel
1st Channel
Sector B
Sector C
Sector A
37
4.2.2
4.2.2.1
IFHO Area
Internal Use Only
According to Figure 4-16, the IFHO area is between Sector A and Sector B. But the IFHO
area is between Sector B and Sector C in DAHHO and MAHHO modes. This is the big
distinction.
4.2.2.2

Generally, when the IFHO area is near Sector B, the signal of Sector A is weak, and the
signal of Sector B is strong, the IFHO is necessary. When the MS is still near Sector A,
the signal of Sector A is strong enough, and the signal of Sector B is weak, the IFHO is
unnecessary.
To avoid the unnecessary IFHO, two parameters are designed in the BSS. These are
T_COMP_HARD_VOICE and T_COMP_HARD_DATA.
These two parameters are on the Handoff Parameter tab at sector level and can be
modified in the NetNumen.
The units, default values, and ranges of these parameters are the same and they are as
follows:
Unit: 0.5 dB
Default value: 1
Range: 0~15
Note:
It is more difficult to trigger the IFHO with a bigger value and easier to trigger the IFHO
with smaller value.
4.2.2.3
Triggering Algorithm
Because the principles of these two parameters are similar, only the triggering Arithmetic
of T_COMP_HARD_VOICE is introduced in the condition of Figure 4-16.
rd
When the MS was in conversation on the 3 carrier, the active set had one PN from
Sector A and the signal strength (Ec/Io) was X dB. Then the MS reported the signal from
Sector B and the signal strength (Ec/Io) was Y dB.
38
Internal Use Only
Now, the BSS constructs two sets. One set is soft handoff set (SHS) and the other is
intra-BSS hard handoff set (Intra-BHHS). The strength (Ec/Io) of SHS is S1 and strength
(Ec/Io) of Intra-BHHS is S2.
In this case, S1 will be X dB, because the pilot beacon cannot bear the traffic. And S2 will
be 10 Log(10^(X/10) + 10^(Y/10)), because the active set can include Sector A and
Sector B if the IFHO is performed.
If (S2-S1) is larger than T_COMP_HARD_VOICE 0.5, the BSS finds that it is worth
performing the IFHO, because the signal of the target carrier is strong. Therefore the
st
BSS will guide the MS to perform the handoff on the 1 carriers of Sector A and Sector B.
rd
Similarly, if the MS was in conversation on the 3 carrier and the active set had two PNs
before the IFHO, their strength (Ec/Io) were X dB and Z dB. The MS reported the strength
of signal from Sector B and its strength (Ec/Io) was Y dB. Now, the BSS constructs two
set. In this case, S1 will be 10 Log(10^(X/10) + 10^(Z/10)) and S2 will be 10
Log(10^(X/10) + 10^(Y/10) + 10^(Z/10)).
39
4.2.2.4
Internal Use Only
Flowchart
Figure 4-17
Process of IFHO in Pilot Beacon Mode
The MS sends
the PSMM to the
BSS.
Other processes,
irrelevant to the IFHO
(pilot beacon mode)
No
Initiate the
handoff?
Yes
Is a new PN from the pilot
beacon?
No
Yes
Construct the SHS and
Intra-BHHS
Calculate S1 and S2
(S2-S1)
>T_COMP_HARD_VOICE?
No
The IFHO is
unnecessary.
Yes
Direct the MS to perform the IFHO
in the Intra-BHHS
The IFHO is
completed.
4.2.3
Configuration Steps
1.
Set the IFHO mode of one carrier sector to pilot beacon.
40
Figure 4-18
2.
Internal Use Only
Setting the IFHO Mode of the Carrier Sector to Pilot Beacon
Add the pilot beacon into the linkcell and NLCS.

In this step, the pilot beacon should be added into the adjacent sectors linkcell and
adjacent carrier sectors neighbor list.
Note:
If the page channel is not configured in the pilot beacon and the pilot beacon is
configured into the NLCS of other carrier sectors, the NGHBR_CONFIG parameter
value of this neighbor sector should be set to 2.
If the page channel is configured in the pilot beacon, the default value 0 of the
NGHBR_CONFIG parameter can be kept.
41
Figure 4-19
3.
Setting NGHBR_CONFIG
Set the parameters T_COMP_HARD_VOICE and T_COMP_HARD_DATA.
Figure 4-20
4.2.4
Internal Use Only
Setting the Threshold Parameters
Neighbor Planning for IFHO (Pilot Beacon)

If the IFHO mode of one carrier sector is set to pilot beacon, its NLCS can be empty.
Because the traffic channel cannot be built on it, even when the pilot beacon has page
channel, the CHANNEL LIST message will not include the channel of pilot beacon and
42
Internal Use Only
the MS cannot continue the pilot beacon in idle state. Therefore, the NLCS is
unnecessary for the pilot beacon.
Regarding the normal carrier sectors of other sites near the pilot beacon, their NLCS may
need to contain the pilot beacon. However, in this case, the neighbor planning is
performed on the same channel, so the procedure described in Chapter 3 can be
followed.
4.2.5
Optimization
4.2.5.1
Addition, Deletion, and Search Priority

Adding the pilot beacon in the NLCS, deleting the pilot beacon from the NLCS, or
modifying the search priority are all based on the handoff counter statistics. The neighbor
sector is important if its handoff counter is ahead of other handoff counters.
4.2.5.2
Tuning the Coverage

The triggering arithmetic is discussed in Section 4.2.2.3. Actually, the MS and BSS have
no idea about the coverage quality (especially Ec/Io) of the target carrier before the IFHO.
The core idea of pilot beacon mode is that the signal strength of the pilot beacon can
indicate the signal strength of other carriers of the same sector. On the basis of this idea,
when the BSS calculates the strength of Intra-IBHHS (S2), the signal strength information
of the carrier where the pilot beacon happens is adopted.
The RF engineers should try to tune the coverage of the Ec/Io of the forward link of the
pilot beacon and make it the same as or similar to the coverage the Ec/Ios of the forward
links of other carriers, so that the IFHO triggering can be more exact.
If the pilot beacon uses the same parameters settings as those of other carriers, such as
the settings of Cell Power, PILOTCH_GAIN, SYNCCH_GAIN, and PAGECH_GAIN, its
Ec/Io will be better than those of other carriers. The main reasons are listed below.
1.
No traffic channel is on the pilot beacon, so the Io will be smaller.
2.
There is no interference of the same channel from the other side.
Generally, the ways to tune the coverage of the Ec/Io of the pilot beacon are listed below.
1.
Tuning the scaling power of the pilot beacon

ZTE suggests that the scaling power value should be 50% of those of other carriers
in the same sectors.
2.
Tuning the channel gain of the pilot channel or SYNC channel
43
Internal Use Only
Decreasing the gain of the pilot channel can depress the Ec and increasing the gain
of the SYNC channel can make the Io bigger, so the Ec/Io can be decreased.
4.2.5.3
Tuning the Threshold

Section 4.2.2.2 introduces the T_COMP_HARD_VOICE and T_COMP_HARD_DATA
settings.
Their default values are 1, that is to say, 0.5 dB. Tuning rules suggested by ZTE are listed
below.
1.
If the number of legs of the active set before the IFHO is less than or equal to 2, the
radio environment is simple. Therefore these two thresholds can be bigger but they
should not exceed 5 (2.5 dB).
2.
If the number of legs of active set before the IFHO is always more than 2, the radio
environment is complex. Therefore, these two thresholds can be smaller but should
be no less than 3.
3.
If the pilot beacons are distributed on the boundary of the BSS as shown Figure
4-21, the threshold parameters of BSC1 should be smaller and the value is
suggested to be 0.
Figure 4-21
Pilot Beacons Distributed on the BSS Boundary

Inter-Frequency Hard
Handoff
Pilot Beacon
Pilot Beacon
BSS 0
BSC 1
Pilot Beacon
4.
Table 4-1 shows the expected strength (Ec/Io) of the pilot beacon in the case that
the threshold value is 2.5 dB.
44
Table 4-1
Internal Use Only
Expected Pilot Beacon Strength When the Threshold Is 2.5 dB
S1-Strength of Corresponding S2-Expected
Corresponding
Expected Strength
SHS Before
Percentage of
Strength of Intra- Percentage of
(Ec/Io) of Pilot
IFHO (dB)
S1 (%)
BHHS (dB)
Beacon (dB)
S2 (%)
-15
3.16
-12.5
5.62
-14
3.98
-11.5
7.08
-13
5.01
-10.5
8.91
-12
6.31
-9.5
11.22
-11
7.94
-8.5
14.13
-10
10.00
-7.5
17.78
-9
12.59
-6.5
22.39
-8
15.85
-5.5
28.18
-7
19.95
-4.5
35.48
-6
25.12
-3.5
44.67
-5
31.62
-2.5
56.23
-4
39.81
-1.5
70.79
-3
50.12
-0.5
89.13
-16.1
-15.1
-14.1
-13.1
-12.1
-11.1
-10.1
-9.1
-8.1
-7.1
-6.1
-5.1
-4.1
45
Internal Use Only
Neighbors for IFHO (EVDO)

There are also three types of IFHO in EVDO systems: handoff in pilot beacon mode,
DAHHO, and MAHHO. Few networks adopt the first mode because the pilot beacon
cannot bear the traffic and the mobility of the data service users is not as good as that of
the voice service users.
A few EVDO MSs cannot search the PNs of other channels in conversation state,
especially some MSs using MSM5500 or MSM6500. The DAHHO is applied, so as to
satisfy the IFHO requirements if the pilot beacon is not available.
Generally, the MAHHO is used widely, because most of the MSs can search the PNs of
other channels in conversation state.
This chapter will introduce MAHHO mode in detail. Other modes will not be introduced.
5.1
Applicable Scenario
The applicable scenario of MAHHO mode in EVDO is the same as that in CDAM 1X. For
detailed information, see Section 4.1.1.
5.2
Triggering the OFS
5.2.1
Idle state
After the following conditions are met at the same time, the OFS is performed.
5.2.2
1.
Only one PN is in the active set.
2.
The Ec/Io of the pilot in active set is less than 5 dB.
3.
If one pilot is in the candidate set, this signal is not from the current serving
frequency.
4.
The neighbor set has at least one neighbor sector from other frequencies.
Conversation State
After the following conditions are met at the same time, the OFS is performed.
1.
The Ec/Ios of the strongest pilots in the active set and candidate set are less than 5
dB.
46
2.
Internal Use Only
The neighbor set has at least one neighbor sector from other frequencies.
5.3
5.3.1
IFHO Area
See Section 4.1.2.1.
5.3.2

1.
PilotAdd
Unit: 0.5 dB
Default value: 18
Range: 0~63
Note:
It is more difficult to trigger the IFHO with a smaller value and easier to trigger the
IFHO with a bigger value.
2.
PilotCompare
Unit: 0.5 dB
Default value: 5
Range: 32~31
Note:
It is more difficult to trigger the IFHO with a bigger value and easier to trigger IFHO
with a smaller value.
47
Figure 5-1
5.3.3
Internal Use Only
PilotAdd and PilotCompare
Trigger Algorithm
If the BSS receives the ROUTE UPDATE message from the MS, it begins to do the
following operations.
1.
Finding whether the pilot from other frequency is in this message

If the pilot from other frequency is in this message, the BSS continues to perform the
next step.
2.
3.
Judging whether the following three conditions are all met

i.
The Ec/Io of the PN from another frequency is stronger than that of strongest
PN in the active set and the difference is greater than PilotCompare 0.5 dB.
ii.
The Keep field of the PN from the current frequency in the ROUTE UPDATE
message is 0.
iii.
The Keep field of the PN from another frequency in ROUTE UPDATE

message is 1 and the Ec/Io of this PN is greater than PilotAdd (0.5) dB.
Deciding the target frequency If all of the three conditions are met
48
4.
5.3.4
Internal Use Only
Deciding that the active set after the IFHO contains PNs from other frequencies in
the RU and greater than PilotAdd (0.5 dB).
Flowchart
Figure 5-2
Flowchart of the MAHHO in the EVDO System

The BSS receives the
ROUTE UPDATE
message.
The BSS sorts all the
PNs in The ROUTE
UPDATE message
According to their
frequencies.
Is the PN from other

frequencies?
No
Other handoff
processes
Yes
The BSS judges whether the IFHO
happens according to the three
conditions.
No
Yes
The BSS decides the
target frequency.
The BSS decides the

PNs in the active set
after the IFHO.
The BSS sends the

TRAFFIC CHANNEL
ASSIGHMENT message.
The IFHO is
completed.
49
5.4
Internal Use Only
Configuration Steps
There are two steps to complete the MAHHO configuration in the EVDO system.
1.
Configure the neighbor sector from other frequencies into the NLCS.
Section 7.2 introduces how to configure the EVDO NLCS. The field of NBCarrierID
is shown in Figure 5-3 and the frequency of the neighbor carrier sector is marked.
Figure 5-3
2.
Interface of Neighbor Carrier List Configuration
Set the threshold parameters.

See Section 5.3.2.
50
5.5
Internal Use Only
Neighbor Planning and Optimization for MAHHO

The maximum number of the NLCSs in EVDO system is 31 in the case that all the
neighbor sectors are from the same frequency. One neighbor from another frequency
occupies 34 bits and one neighbor from the same frequency only occupies 10 bits. The
capacity of the message is limited, so ZTE suggests that the number of neighbor sectors
from other frequencies in the NLCS should be less than 15.
Regarding the planning in MAHHO mode, the drive test data, simulation result, and CDT
data can be applied to get an exact result. If the topology structure of network is simple,
the principles in Chapter 3 can be followed.
Regarding the optimization in MAHHO mode, the following operations should be done.
1.
Removing unnecessary neighbor sectors in the NLCS

Sometimes there may be unnecessary neighbor sectors and this condition can
increase the time that the MS needs to search all the PNs in the CFSRQM and the
IFHO failure rate.
2.
i.
The RF engineers can get the handoff statistical information which marks the
importance degree of the neighbor sectors. If the handoffs between this
neighbor sector and source sector happen rarely, this unimportant neighbor
sector can be deleted.
ii.
Similarly, if one important neighbor sector with a lot of handoffs is found and it
was not in the NLCS, the RF engineers should add it in the NLCS.
The CDT data can be applied to help the RF engineers. According to the CDT data
and triggering conditions, the IFHO area can be confirmed. For details, see Section
4.1.4.
51
Internal Use Only
Neighbors for Inter-BSC Handoff

Some basic concepts about inter-BSC handoffs are introduced in Chapter 2. In this
chapter, the interface, configuration, and precautions are discussed.
6.1
CDMA 1X System
6.1.1
Introduction of the Configuration Interface
6.1.1.1
BSC Handoff Parameter Configuration

Some common attributes need to be set no matter the target BSC is from ZTE equipment
or other vendors, such as SOWD and TOWD. These common attributes are collected in
BSC Handoff Parameters table at BSC level. For detailed information, see Figure 6-1.
Now the values of these parameters are fixed from the last inter-BSC handoff. Generally
the parameters of this table do not need to be modified unless some especial conditions
happen.
For more information about the configuration parameters, see the Configuration
Parameter Manual (1X Release A).
Figure 6-1
BSC Handoff Parameter Table
52
6.1.1.2
Internal Use Only
Global Neighbor List Table and Global Neighbor Frequency Table

These two tables are correlative. One table defines the neighbor sectors from other BSCs
and another table defines the frequency information of these neighbor sectors. These two
tables are designed in one interface, as shown in Figure 6-2.
The Global Neighbor List table is on the upper side of the interface. If one record is
selected, its frequency information will be shown at the bottom of the interface and all the
information can be added, deleted, or modified.
Figure 6-2
Configuration of Global NL of the CDMA 1X System
Actually the Global Neighbor Frequency table is simple and Global Neighbor List table is
complicated. After you double-click the entry, a dialog box appears. This dialog box
shows all the items of this table, as shown in Figure 6-3.
53
Figure 6-3
Internal Use Only
Information of Global Neighbor List Table
BSC type (marked in yellow) represents vendor names and its definition is the same as
that in BSC Handoff Parameter table (in Section 6.1.1.1). If it is modified, other items
marked in blue will change automatically according to the BSC Handoff Parameter table.
For more information, see the Configuration Parameter Manual (1X Release A).
6.1.1.3
Linkcell and NLCS Configuration

1.

Click the Link Cell tab and click
. Then a dialog box appears.
54
Figure 6-4
The Link Cell Tab
Figure 6-5
Linkcell Configuration Interface
Internal Use Only
The interface shown in Figure 6-5 has two tabs. The tab on the left includes all the
cells in this BSC except those listed as follows.
Using the same PN with the source sector
Using the same PN with the sectors in the linkcell
Similarly, the tab on the right includes all the cells in the Global Neighbor List table
except those listed above.
55
2.
Internal Use Only
Configure the NLCS.

Open the NLCS interface and click
Figure 6-6
NLCS Interface
Figure 6-7
NLCS Configuration Interface
. Then a dialog box appears.
56
Internal Use Only
You can select Local BSS or Foreign BSS in Figure 6-7. This dialog box will
display all the carrier sectors in the linkcell except those listed as follows:
6.1.2
The carrier sectors in the NLCS
The carrier sectors that do not have the same channel with the source carrier
sector
The carrier sectors from other BSSs in the condition of Local BSS being
selected
The carrier sectors from the source BSS in the condition of Foreign BSS being
selected
Planning
Usually, the neighbor planning for inter-BSC handoff can be classified into the following
three styles:
6.1.2.1
1.
The two sectors have the same carriers and all the carriers can bear the traffic.
2.
The two sectors have the same carriers but the IFHO modes of the carrier sectors of
one BSS are pilot beacon.
3.
The two sectors have different carriers and all the carriers can bear the traffic.
Style 1
Figure 6-8 shows the schematic diagram of Style 1. The neighbor planning of the
inter-BSC handoff for all the Sector As carriers is same as the neighbor planning of the
intra-BSC handoff but the configuration steps are different. Similarly, the RF engineers
can perform the neighbor planning for Sector B with the same method.
57
Figure 6-8
Internal Use Only
Schematic Diagram of Style 1
Boundary
Between Carriers
BSS 0
Traffic Carrier
Traffic Carrier
Traffic Carrier
nth Channel
Traffic Carrier
nth Channel
2nd Channel
2nd Channel
1st Channel
1st Channel
Sector A
6.1.2.2
BSS 1
Traffic Carrier
Traffic Carrier
Sector B
Style 2
Figure 6-9 shows the schematic diagram of Style 2. The neighbor planning for all the
carriers of Sector A is the same as that of Style 1; the configuration steps are almost the
th
same too. The only one difference is that the IFHO mode of the n carrier of Sector B
should be set to pilot beacon in Global Neighbor Cells Frequency table of BSS 0, as
shown in Figure 6-10. First, double-click one entry of in the BSS Neighbor Cell table and
then its correlative carriers. Second, choose Yes[1] in the Is beacon indicator list.
Figure 6-9

Boundary
Between Carriers
BSS 0
Traffic Carrier
Traffic Carrier
Traffic Carrier
nth Channel
nth Channel
2nd Channel
2nd Channel
1st Channel
1st Channel
Sector A
BSS 1
Pilot Beacon
Traffic Carrier
Traffic Carrier
Sector B
58
Figure 6-10
Internal Use Only
Setting the IFHO Mode of the nth Carrier of Sector B to Pilot Beacon
th
Because the IFHO mode of the n carrier of Sector B is pilot beacon, it does not need the
neighbor planning. The neighbor planning mode and configuration steps for traffic
carriers of Sector B will be the same as those in Style 1.
6.1.2.3
Style 3
Figure 6-11 shows the schematic diagram of Style 3.
The neighbor planning mode and configuration steps for traffic carriers of Sector B and
Carrier 1~m of Sector A are the same as those in Style 1.
Inter-BSC handoff neighbor sectors are IFHO (DAHHO and MAHHO) neighbor sectors
for Carrier m+1~n of Sector A at the same time. Therefore, the RF engineers perform the
neighbor planning of inter-BSC handoff with the method the same as that described in
Section 4.1.4.
59
Figure 6-11
Internal Use Only
Boundary
Between Carriers
BSS 0
Traffic Carrier
m<n
BSS 1
nth Channel
mth Channel
Traffic Carrier
Traffic Carrier
2nd Channel
2nd Channel
1st Channel
1st Channel
Sector A
Traffic Carrier
Traffic Carrier
Traffic Carrier
Sector B
The configuration steps are listed as below (Suppose Sector B is configured as the IFHO
neighbor sector.).
1.
Configure Sector B in the Global Neighbor List in BSS 0.
2.
Configure Carrier 1~m of Sector B in Global Neighbor Cells Frequency in BSS 0.
3.
Add Sector B of the Global Neighbor List in the linkcell of Sector A.
4.
Configure the Candidate Frequency Table of Sector A. All or part of Carrier 1~m can
be configured in this table in this case.
5.
Configure the carriers of Sector B in the Preferred Neighbor List table of Sector A.
6.1.3
Optimization
6.1.3.1

Adding, deleting, or modifying the inter-BSC handoff neighbor sectors in NLCS are all
based on handoff counter statistics. The neighbor sector is important if its handoff
counter is ahead of other handoff counters.
6.1.3.2
Accurate Information
When the neighbor configuration of the intra-BSC handoff is performed, the BSS can
provide the accurate information. But the condition of neighbor configuration of the
inter-BSC handoff is different. The source BSC cannot provide any information of other
BSCs unless they are configured in the global NL.
60
Internal Use Only
According to many cases, the RF engineers should check the neighbor sector
information of the inter-BSC handoff and make sure that the information is accurate,
especially the information about the PN, CI, and LAC. Errors about the three items
appear frequently, which makes the inter-BSC handoff to be rejected.
Perhaps different vendors have different understandings about the CI and LAC, so it is
necessary to be clear about every vendors definition about the CI and LAC on the A
interface.
6.1.3.3
Tuning Coverage
Three styles of neighbor planning are introduced in Section 6.1.2. The handoff mode of
Style 2 and Style 3 are IFHO, so the RF engineers can refer to Section 4.1.4, Section
4.1.5, and Section 4.2.5 for further information about the tuning coverage of these two
styles. This section only demonstrates the tuning coverage of Style 1.
Inter-BSC handoff can be divided into two modes.
Soft handoff
When the inter-BSC handoff happens between two ZTE BSSs and these BSSs
have been inter-connected, this handoff is soft handoff.
This mode can keep the quality of the network service on the boundary area of the
BSC. Because the soft handoff is adopted, the way of tuning coverage of the
boundary cell is the same as that of the internal cell.
Hard handoff
The inter-BSC handoff happens between ZTE BSS and another vendors
equipment.
The inter-BSC handoff happens between two ZTE BSSs but these BSSs have
not been inter-connected.
Only the signal of one BSS can be in the active set and the signal of another BSS is
considered as the interference. Therefore, the interference from the pilots outside of
the active set cannot be avoided in this mode.
For this mode, ZTE offers the following suggestions.
The boundary of the hard handoff should be planned as the outlying area.
The problem of overshooting should be solved so as to narrow the hard

handoff area.
61
6.1.3.4
Internal Use Only
Bridge Solution
Figure 6-12 shows the interference on the boundary of the inter-BSC hard handoff. To
solve this problem, the RF engineers can add another carrier in the site on the left and all
the MSs should work on this carrier, which can decrease the interference. Carrier F1 of
the site on the left will direct the MS to roam from this site to Carrier F2.
This solution can solve the problem of interference but more frequencies will be occupied.
Therefore, this solution can be applied to some special scenarios.
Figure 6-12
Interference on the Boundary of Inter-BSC Hard Handoff
F2
F1
Interfering each other
Figure 6-13
Carrier F1 Working as a Bridge
F2
F1
6.2
F1
EVDO System
There are three modes for inter-BSC handoff in the EVDO system.
1.
A13
62
Internal Use Only
This kind of handoff is original and simple. This kind of handoff is described as
follows.
2.
After the MS moves to the boundary area of the BSC, the signal becomes
worse and worse, due to the interference from another BSC.
The call drop happens and the MS initializes and locks the signal from another
BSC.
The connection should be built again but the session does not need to be built.
A16
This kind of handoff is used widely. This kind of handoff is described as follows.
3.
The MS moves to the boundary area of the BSC and then detects a strong
signal out of the active set.
The MS reports the strength and phase of this signal to the BSS and then the
BSS directs the MS to perform the inter-BSC hard handoff.
The handoff is completed and the MS and source BSC are disconnected.
A17, A18, and A19

This kind of handoff is used rarely. This kind of handoff is described as follows.
The MS moves to the boundary area of the BSC and then detects a strong
signal out of the active set.
The MS reports the strength and phase of this signal to the BSS and then the
BSS directs the MS to perform the inter-BSC soft handoff.
The handoff is completed and the connection between the MS and source BSC
is maintained.
Though the MS moves to the central area of the new BSC, the correlative data
and signal are still transferred on the IBBE link between the new BSC and
source BSC.
The first mode is the simplest one but its effect is the worst in the three modes.
The third mode is the most robust one but this mode requires many IBBE link resources.
st
rd
The second mode can balance the advantage and shortage of the 1 and 3 mode, so it
is used widely.
Only the IBHH based on the A16 interface is introduced here.
63
6.2.1
Configuration
6.2.1.1
Global NL Configuration in the EVDO System
Internal Use Only
Actually this step is similar to that in the CDMA 1X system. For detailed information about
the step, see Section 6.1.1.2.
Figure 6-14 shows the global NL configuration interface at BSC level. The table on the
upper side defines the neighbor sectors from other BSCs and the lower table defines the
particular frequencies used by the neighbor sector.
Figure 6-14
Configuration Interface of the Global NL of the EVDO System
First, click one entry in the table on the upper side and click
. Then a dialog box
shown in Figure 6-15 appears. Fill the correlative information and a new global neighbor
sector is created.
64
Figure 6-15
Internal Use Only
Adding a Foreign Cell to the Global NL in EVDO
Second, click a new entry in the table on the upper side and the values of this entry are
null in the lower table. Click the lower table and then click
Figure 6-16 appears.
. A dialog box shown in
65
Figure 6-16
Internal Use Only
Adding the Frequency Information for the Global NL
Fill the correlative information and then an available global NL will be created.
6.2.1.2
Configuring the NLCS From the Global NL

For detailed information, see Section 7.2.1.
6.2.2
Planning
For detailed information, see Section 6.1.2.
6.2.3
Optimization
6.2.3.1

Adding, deleting, or modifying the inter-BSC handoff neighbor sectors in the NLCS are all
based on the handoff counter statistics. The neighbor sector is important if its handoff
counter is ahead of all handoff counters.
6.2.3.2
Accurate Information
When the neighbor configuration of the intra-BSC handoff is performed, the BSS can
provide the accurate information. The neighbor configuration of the inter-BSC handoff is
different and the source BSC cannot provide any information from other BSCs unless
they are configured in the global NL.
66
Internal Use Only
According to many cases, the RF engineers should check the neighbor sector
information of the inter-BSC handoff and make sure that it is accurate, especially the
information about the PN, color code, and subnet. Errors about the three items appear
frequently, which makes the inter-BSC handoff to be rejected.
6.2.3.3
Tuning Coverage
Three styles of neighbor planning are introduced in Section 6.1.2. This section only
demonstrates the tuning coverage of Style 1.
Only the signal of one BSS can be in the active set and the signal of another BSS is
considered as the interference. Therefore, the interference from the pilots outside the
active set cannot be avoided in this mode.
For this mode, ZTE offers the following suggestions.
1.
The hard handoff boundary should be planned as the outlying area.
2.
The overshooting problem should be solved so as to narrow the hard handoff area.
67
Neighbor Optimization on the

NetNumen
7.1
CDMA 1X System
Internal Use Only
This chapter mainly introduces the optimization of linkcells and NLCSs on the NetNumen.
For details about the optimization of NLIFHOs and global NLs, see the CDMA 1X
Multi-Carrier Network Optimization Guide and Hard Handoff Optimization Guide.
There are two ways to optimize linkcells and NLCSs: optimization without handoff
statistics and optimization with handoff statistics. Usually, the second way is applied to
neighbor optimization while the first way is applied to initial neighbor configuration.
7.1.1
Optimization Without Handoff Statistics
7.1.1.1
Adding a Neighbor
Scenario Description
Source sector: BTS 1-Sector 0, CI- 30010, PN 255, with two carriers
Target sector: BTS 29-Sector 2, CI 30292, PN 315, with two carriers
Part 1: Configuring the Linkcell

Figure 6-4 shows how to open the CDMA 1X linkcell configuration interface and Figure
7-1 shows this interface. It comprises the Local BSS Cell and Foreign BSS Cell tabs.
Because the contents of the Foreign BSS Cell tab have been introduced in Section
6.1.1.3, this section will introduce the Local BSS Cell tab.
68
Figure 7-1
Internal Use Only
CDMA 1X Linkcell Configuration Interface
The Local BSS Cell tab lists all the sectors of this BSS except the following sectors:
The sectors that use the same PN with the source sector.
The sectors that have already been configured in the linkcell.
The sectors that use the same PNs with the sectors in the linkcell.
Several sectors use PN 315, but their CIs are different, as shown in Figure 7-1. Select the
right one (BTS 29-Sector 2) and click OK. Then it will be added to the linkcell of BTS
1-Sector 0.
Tip:
1.
You can identify each sector not only by the value of the CI parameter but also by
that of the System or Cell parameter.
2.
Double-click a column heading. Then the contents of this table will be sorted
automatically. In Figure 7-1, the table contents are sorted by the Pilot PN parameter.
Press and hold CTRL, and double-click another column heading. Then the contents
will be sorted by multiple parameters.
3.
To add more than one neighbor to the linkcell at the same time, select one neighbor,
press and hold CTRL, and click the other neighbors that you also want to add.
However, sectors using the same PN cannot be selected at the same time.
4.
If the Enable reverse configuration when adding neighbor cell check box is
selected, the source sector will be added to the linkcell of each selected sector
unless this linkcell already contains a sector using the same PN with the source
sector.
69
5.
Internal Use Only
Before adding a carrier sector to the NLCS, you should first add this sector to the
linkcell.
Part 2: Configuring the NLCS

Take this step after BTS 29-Sector 2 has been added to the linkcell of BTS 1-Sector 0.
Figure 6-6 shows how to open the CDMA 1X NLCS configuration interface. Do not select
the Add neighbor list with handoff information check box. Otherwise, you will be on
the second way of optimization, that is, optimization with handoff statistics.
Figure 7-2 shows the NLCS configuration interface. This interface has two options: Local
BSS and Foreign BSS. Because the contents for the Foreign BSS option has been
introduced in Figure 6-7, this section will introduce the contents for the Local BSS option.
Figure 7-2
CDMA 1X NLCS Configuration Interface
The NLCS configuration interface lists all the carrier sectors in the linkcell of the target
carrier except for the following cases:
Sectors are in the linkcell but they do not have a carrier on the same channel of the
target carrier.
The corresponding carriers of the sectors in the linkcell have been configured in the
NLCS.
70
Internal Use Only
As shown in Figure 7-2, find PN 315 and then add this carrier sector to the NLCS.
Tip:
7.1.1.2
1.
You can sort the table contents by multiple parameters.
2.
You can identify each neighbor not only by the PN parameter but also by the
NcellSystemid or NCellid parameter.
3.
To add more than one neighbor to the NLCS at the same time, select one neighbor,
press and hold CTRL, and click the other neighbors that you want to add.
4.
The maximum number of neighbors in an NLCS is 20. It means that when only one
PN is in the active set, the maximum number of neighbors in the NLCS is 20.
However, if the MS is in handoff state, the maximum number can be 40.
5.
The items marked in green in Figure 7-2 can be ignored unless you need to use the
search priority and frequency functions.
6.
If the Configure each other when adding neighboring sector check box is
selected, the source carrier sector will be added to the NLCS of each selected
carrier sector unless this NLCS already contains a carrier sector using the same PN
with the source carrier sector.
Deleting a Neighbor
Scenario Description
Source sector: BTS 1-Sector 0, CI 30010, PN 255, with two carriers
Target sector: BTS 29-Sector 2, CI 30292, PN 315, with two carriers
BTS 29-Sector 2 is in the linkcell of the source sector, and carrier sectors of BTS
29-Sector 2 are in the NLCSs of the source carrier sectors.
Part 1: Deleting a Neighbor From the NLCS
Open the NLCS configuration interface. Right-click a neighbor that you want to delete
and choose Delete from the shortcut menu.
71
Figure 7-3
Internal Use Only
Deleting a Neighbor From the CDMA 1X NLCS Without Handoff Statistics
Then the NetNumen will ask you whether to delete bidirectional NLCS relations. If you
choose Yes, not only PN 315 will be deleted from the NLCS of BTS 1-Sector 0, but also
PN 255 will be deleted from the NLCS of the correlative carrier sector of BTS 29-Sector 2.
Wrong neighbor configurations should be deleted. For example, if two sectors are
far from each other, we suggest deleting the bidirectional neighbor relations.
Sometimes, less important neighbor configurations should be deleted. For example,

if an NLCS is full, we suggest deleting unidirectional relations only.
Figure 7-4
Deletion of Bidirectional Neighbor Relations
Tip:
1.
You can delete more than one neighbor from an NLCS at the same time.
72
Internal Use Only
2.
The sector is still in the relevant linkcell after this operation is completed.
3.
Part 2: Deleting a Neighbor From the Linkcell

Open the linkcell configuration interface. Right-click the neighbor you want to delete and
choose Delete Neighbor Cell from the shortcut menu.
Figure 7-5
Deleting a Neighbor From the CDMA 1X Linkcell Without Handoff Statistics
Then the NetNumen will ask you whether to delete bidirectional linkcell relations. If you
choose Yes, not only PN 315 will be deleted from the linkcell, but also PN 255 will be
deleted from the linkcell of BTS 29-Sector 2.
Wrong neighbor configurations should be deleted. For example, if two sectors are
far from each other, we suggest deleting the bidirectional neighbor relations.
Sometimes, less important neighbor configurations should be deleted. For example,

if a linkcell contains too many neighbors, we suggest deleting unidirectional
relations only.
Tip:
1.
You can delete more than one neighbor at the same time.
2.
73
3.
Internal Use Only
Suppose A and B are two sectors, A1 and A2 are As carrier sectors, B1 and B2 are
Bs carrier sectors, B has been configured in the linkcell of A, and B1 has been
configured in the NLCS of A1, and B2 has been configured in the NLCS of A2. If B is
deleted from the linkcell of A directly, all the carrier sectors of B like B1 and B2 will
be removed for the NLCSs of A.
7.1.2
Optimization With Handoff Statistics
7.1.2.1
Startup
Open the CDMA 1X NLCS configuration interface. Before clicking
, you need to select
the Add neighbor list with handoff information check box, as shown in Figure 7-6.
Figure 7-6
7.1.2.2
Starting CDMA 1X Neighbor Optimization With Handoff Statistics
Parameter Setting
The parameters marked in yellow in Figure 7-7 should be set as follows:
1.
Set the neighbors that are to be optimized.
2.
Set the begin time and end time of the handoff statistics.
3.
Set whether bidirectional neighbor relations are needed.
74
Internal Use Only
i.
If the Linkcell configure each other check box is selected, after one target
sector is added to the linkcell of the source sector, the NetNumen will try to add
the source sector to the linkcell of this target sector.
ii.
If the Neighbor carriers configure each other check box is selected, after
one target carrier sector is added to the NLCS of the source carrier sector, the
NetNumen will try to add the source carrier sector to the NLCS of this target
carrier sector.
Usually, we do not suggest selecting these two check boxes unless bidirectional
neighbor relations are necessary.
4.
Click Advanced. A dialog box will appear, as shown in Figure 7-8. Advanced
settings will only influence the upper table of Figure 7-7.
i.
Is local BSS cells, Is Other BSS cells and All cells: Usually, keep the default
setting All Cells. If the Is local BSS cells option is chosen, the upper table will
only list correlative sectors of the local BSS and if the Is other BSS Cells
option is chosen, the upper table will only list correlative sectors of other BSSs.
ii.
If the Is in linkcell check box is selected, the upper table will only list
correlative sectors that are in the linkcell.
iii.
You can select the Use max distance check box and fill in a number. Then the
upper table will only list the corresponding sectors, that is, the distances
between these sectors and the source sector are not longer than this maximum
distance.
iv.
You can select the Use Min Number of handoff check box and fill in a number.
Then only when the number of handoffs of a neighbor is more than or equal to
this number can this neighbor be displayed in the upper table.
v.
You can select the Use Min difference of PN check box and fill in a number.
For example, if the PN of the source carrier sector is X and this number is set
to Y, the upper table will list all the corresponding neighbors using PNs that are
greater than X + Y or smaller than X Y.
Usually, default settings are used for advanced settings.
75
Internal Use Only
Figure 7-7 Parameter Setting of CDMA 1X Neighbor Optimization With Handoff

Statistics
Figure 7-8 Advanced Settings of CDMA 1X Neighbor Optimization With Handoff

Statistics
7.1.2.3
Meanings of the Parameters on the Neighbor Optimization Interface

Figure 7-9 contains two tables. The lower table shows the NLCS of the source carrier
sector; the upper table shows all the carrier sectors that have handoff with the source
carrier sector except those in the NLCS. The lower table can be called NLHST
(Neighbor List Handoff Statistic Table); the upper table can be called RSHST
(Remaining Set Handoff Statistic Table).
76
Figure 7-9
Internal Use Only
CDMA 1X Neighbor List Optimization Interface
Parameters in the NLHST

1.
BTS: number of the BTS to which the neighbor carrier sector belongs. If this
neighbor carrier sector is of another BSS, the value of this parameter will be null.
2.
BTS_Alias: alias of the BTS to which the neighbor carrier sector belongs. If this
3.
Cell: number of the sector to which the neighbor carrier sector belongs. For
example, if the value of the Cell parameter of alpha sector is 0, that of beta sector
will be 1. If the neighbor carrier sector is of another BSS, the value of this parameter
will be null.
4.
Alias: alias of the sector to which the neighbor carrier sector belongs. If this
5.
Pilot _pn: pilot number of the neighbor carrier sector
6.
Distance: distance between the source carrier sector and neighbor carrier sector.
This value can be calculated on the basis of longitudes and latitudes of the two
carrier sectors. If the longitudes and latitudes are accurate, the value of the
Distance parameter will be correct; otherwise, the output will be incorrect and affect
the optimization results.
77
Internal Use Only
7.
Handoffcount: number of handoff attempts between the neighbor carrier sector

and source carrier sector. If the source carrier sector is already in the active set and
then the MS tries to add the neighbor carrier sector to the active set, this value will
increase by one.
8.
Successhandoffcount: number of success handoffs between the neighbor carrier

sector and source carrier sector. If the source carrier sector is already in the active
set and then the MS manages to add the neighbor carrier sector to the active set,
this value will increase by one.
9.
Srch_win_nghbr: size of the window for the MS to search neighbors. If the

GENERAL NEIGHBOR LIST, EXTENDED NEIGHBOR LIST, and UNIVERSAL
NEIGHBOR LIST messages are used and the value of the NGHBR_CONFIG
parameter is 10 or 11, the Srch_win_nghbr parameter is available.
10. Isreversecfg: This parameter indicates whether the NLCS of the neighbor carrier
sector contains the source carrier sector. If it contains the source carrier sector, this
parameter value will be 1; otherwise, it will be 0.
11. Locked: This parameter indicates whether the neighbor carrier sector is locked or
not. If it is locked, the parameter value will be 1; otherwise, it will be 0. For details,
see Section 8.1.
12. GncellID: If the neighbor carrier sector belongs to the source BSS, the value of this
parameter will be null; otherwise, it will be the same as the value of GNCELLID in
the global NL. For details, see Section 2.1.4.
Parameters in the RSHST
1.
Parameters 1~8 and 12 are the same as those in the NLHST.
2.
Isinlinkcell: This parameter indicates whether this neighbor is in the linkcell. If it is

in the linkcell, this parameter value will be 1; otherwise, it will be 0.
3.
Isreversecfg: If the value of the Isinlinkcell parameter is 0, the value of this

parameter will be 0 too. If the value of the Isinlinkcell parameter is 1, this parameter
will indicate whether the linkcell of the neighbor sector contains the source sector. If
it contains the source sector, this parameter value will be 1; otherwise, it will be 0.
4.
Ncellmode: This parameter indicates whether this sector is working in normal cell
mode or boomer cell mode. If it is working in normal cell mode, this parameter value
will be 0; otherwise, it will be 1.
An RSHST may contain several entries and every entry represents one carrier
sector. These entries are based on the global NL or data of the source BSS. If the
source carrier sector is in the active set of the MS and the MS requests to perform
handoff, the following events may occur:
78
Internal Use Only
i.
If this PN is already in the NLCS of the source carrier sector, this handoff will
be counted in the NLHST; if this PN is not in NLCS, this handoff will be counted
in the RSHST.
ii.
If this PN is not in the NLCS but in the linkcell, the handoff will succeed and this
handoff will be counted in one carrier sectors entry in the RSHST.
iii.
If this PN is not in the linkcell, the handoff will fail because the BSS cannot
identify the target sector. As a result, the BSS will list all the sectors in the
source BSS and global NL that use the same PN in the RSHST, and counters
of all these sectors will increase by one.
iv.
According to the above Item (i), if one PN is already in the NLHST, usually it
will not appear in the RSHST. However, there are exceptions, as shown in
Figure 7-10.
N01 and N02 are in the NLCS of the source carrier sector (S1); N12 is not in
the NLCS of the source carrier sector but in the NLCS of N01; the PN of N12 is
the same as that of N02. This configuration is abnormal, and the possible
reasons include:
a)
The PN reuse distance between N02 and N12 is too short.
b)
Although the PN reuse distance is long enough and N12 is far away from
the other three sectors, as shown in Figure 7-10, there is something
wrong with the configuration: N12 has been added to the NLCS of N01.
If S1 and N01 are in the active set of the MS, when the MS requests to add one
PN from N02 to its active set, the BSS cannot identify whether this PN is from
N02 or N12. Sometimes its choice is wrong and N12 is added to the active set.
Because N12 is not in the NLCS of S1, N12 will appear in the RSHST. Hence
the RSHST and NLHST contain two different carrier sectors using the same
PN.
79
Figure 7-10
Internal Use Only
Scenario That the Same PN Appears in Both the NLHST and RSHST
S1
Source Carrier Sector
N01
MS
N02
N12
v.
According to the above Item (iii), handoff will fail if the PN reported by the MS is
not in the linkcell. But you can find that the handoff success numbers of some
neighbors are not zero. Usually, it happens in the scenario shown in Figure
7-11. S1 is the source carrier sector; N01 is in the NLCS of S1; N12 is not in
the NLCS of S1 but in the NLCS of N01.
If only S1 is in the active set, the MS will report that the PN of N12 is in its
remaining set and hence the handoff will fail. However, if S1 and N01 are in the
active set, the MS will report that the PN of N12 is in its neighbor set because
N12 is in the NLCS of N01 and hence the handoff will succeed.
80
Internal Use Only
Figure 7-11 Scenario That the Handoff Succeeds Even If the MS Reports That the PN
Is in Its Remaining Set
S1
Source Carrier Sector
N01
MS
N12
7.1.2.4
Optimization Actions
Sorting neighbors by sequence

Click Optimize in Figure 7-9. Then the NetNumen will sort the contents of NLHST
by number of handoffs in a descending order. For more information about sequence
sorting, see Section 8.2.
Deleting an unnecessary neighbor from the NLCS

i.
Evaluate the importance of each neighbor in the NLCS according to its handoff
statistics and distance. If one neighbor is far from the source carrier sector or if
it has a very small number of handoffs, it can be deleted from the NLCS.
ii.
Right-click the neighbor that you want to delete and choose Delete From
Neighbor List from the shortcut menu, as shown in Figure 7-12. And the
NetNumen will ask whether to delete reverse neighbor relations or not, just as
shown in Figure 7-4.
81
Figure 7-12
Internal Use Only
Shortcut Menu for Deleting a Neighbor From the NLHST
Other commands on the above shortcut menu are applicable to the following
scenarios:
Neighbor Cell Reverse Configure and Delete Reverse Configured

Neighbor Cell: The current neighbor configurations are reasonable, but the
RF engineers want to add the source carrier sector to or delete it from the
NLCS of its neighbor carrier sector. The operation procedures are similar to
that of removing unnecessary neighbors from the NLCS.
Lock and Unlock: The RF engineers want to lock or unlock entries of the
NLCS. For details, see Section 8.1.
Deleting an unnecessary neighbor from the linkcell

i.
Open the dialog box of advanced settings (see Figure 7-8) and clear the Use
min number of handoff check box.
The RSHST can be sorted by multiple parameters, which means that you can
sort this table by the Isinlinkcell and Handoffcount parameters. Please note
that the Isinlinkcell parameter has a higher priority than the Handoffcount
parameter.
The neighbors that belong to the linkcell but have small Handoffcount
parameter values can be deleted from the linkcell.
ii.
Right-click the neighbor that you want to delete and choose Delete From Link
Cells, as shown in Figure 7-13.
82
Figure 7-13
7.2
Internal Use Only
Shortcut Menu for Deleting a Neighbor From the Linkcell
Adding a necessary neighbor to the NLCS

i.
Sort the RSHST by the Handoffcount parameter in a descending order to find

the top N neighbors with large handoff numbers. If several neighbors use a
same PN, decide which should be the right one according to the Distance
parameter values and other information.
ii.
Right-click the neighbor that you want to add and choose Add As Neighbor
List, as shown in Figure 7-13.
EVDO System
Neighbor configuration operations of EVDO systems are quite similar to those of CDMA
1X systems.
7.2.1
Optimization Without Handoff Statistics

Log on to the NetNumen for ZXC10 BSSB. Choose an EVDO carrier on the left
navigation tree, click the Neighbor Carrier List tab in the right DO Carrier Parameters
pane, and click
to open the EVDO neighbor carrier list configuration interface, as
shown in Figure 7-14.
83
Figure 7-14
Internal Use Only
Opening the EVDO Neighbor Carrier List Configuration Interface
A dialog box as shown in Figure 7-15 will appear. Choose the appropriate neighbors and
click OK.
84
Figure 7-15
Internal Use Only
EVDO Neighbor Carrier List Configuration Interface
To delete unnecessary neighbors from the NLCS, select the corresponding entries in
Figure 7-14 and click
7.2.2
Optimization With Handoff Statistics

If you have selected the Add Neighbor List With Handoff Information check box in
Figure 7-14 before clicking
, a new interface as shown in Figure 7-16 will appear.
Similar to the CDMA 1X neighbor list optimization interface (see Figure 7-9), this EVDO
neighbor optimization interface also contains two tables: NLHST and RSHST.
85
Figure 7-16
Internal Use Only
EVDO Neighbor Optimization Interface With Handoff Statistics
The principles and methods of neighbor optimization based on NLHSTs and RSHSTs are
similar to those in Section 7.1.2.
86
Other Useful Functions
8.1
Neighbor Locking and Unlocking
Internal Use Only
Sometimes one neighbor does not have a large number of handoffs and thus is not listed
among the top N neighbors in the NLCS, but it may be very important to the quality of
service for VIPs for example, a neighbor sector that is in an indoor distribution system
and covers a famous hotel. To avoid deleting this kind of important neighbors, the RF
engineers can use the neighbor locking and unlocking functions of the NetNumen.
If a neighbor in the NLCS is locked, it cannot be deleted from the NLCS unless it is
unlocked.
Figure 8-1 shows how to lock a neighbor on the NetNumen: Right-click the neighbor that
you want to lock and then choose Lock. Then the value of the Locked parameter will
change from 0 to 1, as shown in Figure 8-2.
Figure 8-1
Locking a Neighbor
87
Figure 8-2
Internal Use Only
Indicator for a Locked Neighbor
Similarly, to unlock a neighbor, right-click it and then choose Unlock.

Actually, this attribute can be modified in command-line mode or ODD file mode.
Note:
Neighbors that are locked cannot be deleted from the NLCS but their places in the NLCS
may change due to other operations.
8.2
Neighbor Sequence Sorting

The CDMA protocol has defined the order of neighbor search priority, and NLCSs
support neighbor sequence sorting. Usually, the place of a neighbor in an NLCS can
reflect its importance.
Note:
The MS searches neighbors in the NLCS by sequence. If a neighbor is listed at the end of
the NLCS, it will be searched later.
When the MS is in handoff state, the BSS will integrate the NLCSs of several available
carrier sectors in the active set of the MS and send a final NLCS to the MS. However, the
88
Internal Use Only
maximum number of neighbors in an NLCS is limited. As a result, the neighbors at the

end of the NLCSs will be discarded probably.
The NetNumen supports automatic neighbor sequence sorting. This function is based on
handoff statistics of every neighbor sector in the NLCS and this function will not lead to
addition or deletion of neighbor sectors.
1.
Because this function is disabled on the NetNumen by default, you need to enable it
first, as shown in Figure 8-3.
Figure 8-3
2.
Enabling Automatic Neighbor Sequence Sorting
Then a dialog box will appear, as shown in Figure 8-4.

i.
Set the range of BTSs in the BTS number text box.
ii.
Set the start time and end time. These two time settings mean the start point
and end point of handoff statistics.
iii.
If you want to put softer handoff neighbors ahead, select the Softer handoff
precedence check box.
89
Figure 8-4
Internal Use Only
Setting Automatic Neighbor Sequence Sorting
Note:
This function will modify the configuration data but will not cause synchronization.
Because sequence sorting takes a lot of system resources, we do not suggest performing
this operation when the system is busy.
Because sequence sorting may take a long time, you need to wait with patience.
In addition, the NetNumen provides a shortcut menu for you to adjust the neighbor
sequence in the NLCS at carrier sector level.
Figure 8-5
Shortcut Menu for Sequence Adjustment
90

CDMA RNO Subject-Neighbor Planning and Optimization Guidelines - R1 (1) .0

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

CDMA RNO Subject-Neighbor Planning and Optimization Guidelines - R1 (1) .0

Transféré par

Droits d'auteur :

Formats disponibles

CDMA Neighbor Planning and

CDMA Neighbor Planning and Optimization Guidelines

Internal Use Only

http://dms.zte.com.cn (Technical Support)

ZTE Confidential Proprietary

2011 ZTE CORPORATION. All rights reserved.

CDMA Neighbor Planning and Optimization Guidelines

Internal Use Only

Reason for Revision

ZTE Confidential Proprietary

2011 ZTE CORPORATION. All rights reserved.

CDMA Neighbor Planning and Optimization Guidelines

Internal Use Only

Intended audience: CDMA RF engineers

Knowledge and skills

Basic theory of the CDMA technology

Signaling flow of handoff

Operation practice of ZTEs CDMA

CDMA 1X Multi-Carrier Network

A guide to the optimization of CDMA 1X

NetMAX Operation Guide

A guide to the NetMAX operations

Hard Handoff Optimization Guide

A guide to the optimization of hard handoff

Configuration Parameter Manual (1X

A guide to the configuration parameters (1X

ZTE Confidential Proprietary

2011 ZTE CORPORATION. All rights reserved.

CDMA Neighbor Planning and Optimization Guidelines

Internal Use Only

About This Document

Introduces the document briefly, including its objectives and

Describes the neighbor lists in CDMA 1X and EVDO systems.

Principles for Neighbor Planning

Describes the basic principles for neighbor planning.

Neighbors for IFHO (CDMA 1X)

Describes the neighbors for IFHO in CDMA 1X systems.

Neighbors for IFHO (EVDO)

Describes the neighbors for IFHO in EVDO systems.

Neighbors for Inter-BSC Handoff

Describes the neighbors for inter-BSC handoff in CDMA 1X

7 Neighbor Optimization on the

Describes neighbor optimization operations on the

Describes some other useful functions.

Other Useful Functions

ZTE Confidential Proprietary

2011 ZTE CORPORATION. All rights reserved.

CDMA Neighbor Planning and Optimization Guidelines

Internal Use Only

Principles for Neighbor Planning ................................................................ 16

Neighbors for IFHO (CDMA 1X) ................................................................... 19

Neighbors for IFHO (EVDO) ......................................................................... 46

ZTE Confidential Proprietary

2011 ZTE CORPORATION. All rights reserved.

CDMA Neighbor Planning and Optimization Guidelines

Internal Use Only

Threshold Parameter Setting .......................................................................... 47

Neighbors for Inter-BSC Handoff ................................................................ 52

Neighbor Optimization on the NetNumen ................................................... 68

Other Useful Functions ................................................................................ 87

ZTE Confidential Proprietary

2011 ZTE CORPORATION. All rights reserved.

CDMA Neighbor Planning and Optimization Guidelines