SAMSUNG

TELECOMMUNICATIONS
AMERICA (STA)

Neighbor Definition and Creation

Process
Apr 2012

(STA)
(STA)Samsung
SamsungTelecommunications
TelecommunicationsAmerica.
America.All
AllRights
RightsReserved.
Reserved.Confidential
Confidentialand
andProprietary.
Proprietary.

High level Nbr definition

Define SHO
Nbr before
CLA

Test freq CLA

Nbr list

IVHHO and SHO

nbrs prioritized
based on legacy
HO count

Pre Mig 2
Nbr list

(STA)Samsung Telecommunications America. All Rights Reserved. Confidential and Proprietary.

Post migration
nbr modifications

Post migration
Nbr mods

Nbr list modification process

If nbrs relations to be modified are less than 15 for a BSC ask Samsung TAC to define them
through GUI (Manually without script)
Take the latest nbr dump for applicable BSC, retain BTSs which needs modification, make
modifications and make sure Indexes are in ascending order starting from 0.
Ask Samsung TAC to replace the existing nbr list for applicable BTSs.
Every nbr change requires non service impacting FYI CMC ticket.
Nbr relation changes for upto 4 sites in a day per cluster can be implemented in day time while
for more the implementation needs to happen in Maint window.
Audit the nbr dump received from Samsung TAC against the list provided for implementation.

(STA)Samsung Telecommunications America. All Rights Reserved. Confidential and Proprietary.

High level nbr creation process

SHO Neighbors are directly pulled out of Legacy network (HOM), converted to Samsung
format for SOURCE - TARGET relations and are supposed to be in place at the CTTP
phase (before CLA).
IVHHO Neighbors are defined based on the Legacy HO matrix, significant NL relations are
retained and converted to Samsung format. The process is outlined in subsequent slides
Append the new IVHHO NL to the existing SHO NL and prioritize them based on existing
Legacy HO count (You can alternatively use the current HOM matrix to create a compete
new nbr list prioritized based on HO counts)
A complete Neighbor List, combination of SHO and IVHHO NL based on priority levels are
supposed to be in place at least 1 day before migration date.
With this process Samsung will decide the IVHHO nbr list and provide this list to EMS for
implementation from their end.
1x Nbr lis t - Format

(STA)Samsung Telecommunications America. All Rights Reserved. Confidential and Proprietary.

EvDO Nbr lis t Format

Required Input for nbr creation

Prepare vendor based boundaries with sites listed on Mapinfo Eg. Samsung, Motorola, Nortel,
Lucent
List and highlight all the neighboring vendors of the migrating cluster
Obtain the legacy HO matrix from EMS for the applicable BSC.
Playbook and Samsung Channel plan
Have the SID, NID and the channel information and the number of carriers information for
both Legacy and Samsung sites from the playbook and channel plan respectively.
Obtain the final SAMSUNG format for NL

(STA)Samsung Telecommunications America. All Rights Reserved. Confidential and Proprietary.

Nbr list creation using HOM before CLA

Retain the existing f1-1X channel related neighbors and delete all other neighbors at this point
of time.
Have the existing clusters sites in the source and target BTS and delete all the other sites
from the list (delete entire rows)
Any nbr relation having more than 6 HO attempts should be retained in the nbr list.
Change Source and target (Samsung) sector to (0/1/2) format
Obtain the relevant PN for target sectors
Enter Samsung NID,SID and change the nbr list format to Samsung nbr list for EvDO and 1X.
Copy 1x NBR list twice once for Band class 0 and then for band class 1. Nbr list is ready

(STA)Samsung Telecommunications America. All Rights Reserved. Confidential and Proprietary.

Nbr list creation using HOM before migration after

CLA
Retain the existing f1-1X channel related neighbors and delete all other neighbors at this point
of time.
Have the existing clusters sites in the source BTS and delete all the nbr relations where
target belongs to migration cluster.
Change Source (Samsung) sector to (0/1/2) format
Obtain the relevant PN for target sectors and the no. of carriers for both the source and target
sectors.
Delete all the columns except Samsung (BTS ID, Sector ID, No of carriers) legacy (BTS ID,
Sector ID, PN, cascade id, No. of carriers and handover attempts)
This list would to be used for IVHHO nbr list creation.

(STA)Samsung Telecommunications America. All Rights Reserved. Confidential and Proprietary.

Nbr list creation using HOM before migration after

CLA
IVHHO Nbr list creation
For IVHHO nbrs sum the outgoing HO counts for each Source sector and get a percentage contribution
for each nbr relation (only for IVHHO nbrs).
Retain the top contributors with HO contribution above 2% for 800 MHz and above 3% or more than 500
attempts for 1900 MHz
The source sectors having low total HO count can be visually verified in the map. If the site is in the core
of Samsung cluster, delete all the nbr relations for this site .

Append IVHHO nbr list to SHO nbr list for PCS (Band class 1) and Cellular (band class -0).
Remove nbr relations for source BTSs which does not have 800 capability (Hot swaps). Pl note
that the SHO nbr list should have handover counts.
Sort the list by Band class, Samsung BTS ID, Sector ID (A to Z) and HO count (Highest to
lowest) and then add the indexes per sector in ascending order starting from 0.

(STA)Samsung Telecommunications America. All Rights Reserved. Confidential and Proprietary.

Nbr list creation using HOM before migration after

CLA
For 800 Nbr list all the IVHHO nbr relations should have search set = 1. For all the SHO nbr
relations it should be 0. For intra Samsung IFHO follow the steps mentioned in later slides
For 1900 all the sectors with higher number of carriers than target has the SEARCH SET
column set to 1 while the rest would be 0
Use all the SHO nbrs to create basic EvDO nbr list. Use the later slide to prepare the DO nbr list
based on carrier count fro IFHO perspective.
The nbr list is ready to be sent to Samsung TAC.
Swap the source and target cells/PNs for HO type 6 nbrs to provide nbr list to EMS. Do
remember to change the sector ids to alpha, beta, gama (instead of 0/1/2) for Samsung sectors.
For Vendors just supporting RTD based IVHHO the nbr list from legacy to Samsung needs to
be curtailed to one legacy sector to one Samsung nbr based on highest priority relation.
Audit the nbr dump received from Samsung TAC against the list provided for implementation.

(STA)Samsung Telecommunications America. All Rights Reserved. Confidential and Proprietary.

Nbr list changes to the existing SHO nbr

list 1X IVHHO
The format for the IVHHO nbrs is attached.
Following are the points to consider (Shaded yellow in the sheet)
The NNID is Legacy switch no.
The NSID should be carefully entered.
The sector ID for legacy vendors is 1/2/3 and not 0/1/2
Search set should be set to 1 only for IFHO
The HO_Type for IVHHO is 6. For remaining nbr relations it should be 1.
nConfig should be defined per guideline
Nbr priority should be based on legacy HO attempts

Nbr lis t for 1X

IVHHO

(STA)Samsung Telecommunications America. All Rights Reserved. Confidential and Proprietary.

Nbr list changes 1X IFHO

1) Look up the number of carriers for source and target cell as in the attached sheet.
2) Wherever there is scope of IFHO from source to target, define search set to 1.
Samsung source has more carriers than target (Legacy or Samsung)
Samsung has different carrier from legacy

IFHO
parameters

Search set enables BTS to send

CFSRM. If search set is 0 no IFHO
will take place

IF_IVHHO_Scenario

(STA)Samsung Telecommunications America. All Rights Reserved. Confidential and Proprietary.

border carr
definition template

Nbr addition for Idle handoffs to Femto

Please find below nbr list to be appended to nbr definition of every nbr along with IVHHO nbrs pre
migration.
Every commercial site in the network has to have these 3 nbrs on both 800 and 1900 1x network. The DO
sectors also need to have these nbrs.
The NNID for all the Femto cells should be 0.
The only thing in this nbr list changes from one site to other is SID. The source and target SID should be
same.
Pl note that priority for these nbrs has to be 20/21/22 across the network.
The BTS ID is fixed as 65535 and sector IDs are 253/254/255.
The Nconfig for 1x nbr list needs to be changed to either 0 or 1. If the source has PCH count more
than 1 than nconfig will be 1 else 0. The nbr of carrier between macro source and FEMTO target is always
assumed to be same as Femto hops on all the available macro carriers.

Addimg Femto as
nbrs

(STA)Samsung Telecommunications America. All Rights Reserved. Confidential and Proprietary.

nConfig defintion
S no.
1
2
3
4

Condition

Nconfig

Source and target have different carrier (count) but same PCH channel count per
carr

Source and target have same carrier count and same PCH channel count per carrier

Source and target have different carrier assignment (count) and different PCH
channel count per carrier

Source and target has same carrier count but different PCH Count

Please note that PCH count for target IVHHO nbrs should also be taken into consideration

Num_PCH

Nationwide paging channel count is attached.

For any Samsung site PCH count will be equal to max paging count for any of the 1X carrier in legacy site.
In the cases where legacy nbr has equal no. of carriers as that of source NV, we will have to make sure
that Legacy site has equal no. of PCH count for all the carriers. This applies to sites having more than 1
carrier. In such cases if legacy has different PCH counts among their carriers, they will have to be
requested to make each carrier with as any PCH count as that of carrier with max PCH count

(STA)Samsung Telecommunications America. All Rights Reserved. Confidential and Proprietary.

Intra Samsung IFHO Definition 800 MHz

Take (filter) the existing SHO Nbr list for 800 SHO nbr definition (Band class 0)
Identify the Target BTSs which does not have 800 MHz.
Change Search set to 1 for every nbr relation where target Samsung cell does not have 800
MHz.

(STA)Samsung Telecommunications America. All Rights Reserved. Confidential and Proprietary.

FA level MAHHO parameters

Following FA level parameters: FA_MODE, HANDDOWN_FA_LO, HANDDOWN_FA_HI,

HANDDOWN_BANDCLASS can be configured via CHG-BTS_SUBCELL_PARA command from BSM.
For example, to configure inter-frequency MAHHO from CDMA channel number 375 (FA_ID =15) to 350 (FA_ID =14) for PCS
band BTS 311 sector alpha, one would set FA_MODE of BTS 311, sector 0, FA_Index =3 (corresponding to CDMA channel
number 375) to border FA, HANDDOWN_FA_LO = 2^14=16384, HANDDOWN_FA_HI = 0.

If FA_ID of the nbr cell is lower than 32 then the FAID value is taken from parameter HANDDOWN_FA_LO,
Otherwise it is taken from HANDDOWN_FA_Hi.
Refer the IFHO call flow for further information

(STA)Samsung Telecommunications America. All Rights Reserved. Confidential and Proprietary.

EvDO IFHO Neighbor list changes

1) Pl note IVHHO is not supported for EvDO.
2) Use 1X SHO Nbr list, delete all the source sectors on band class 0. Convert the list into
DO format.
3) Lookup the no. of DO carriers for both source and target carrier.
4) Change 3 parameters for all the nbrs having IFHO (more carriers in source than target).
NCHANNEL_INCL =1 NCHANNEL = Common carrier and NBAND =1.
5) The nbrs needs to be duplicated if there are more than 1 carriers in the target cell and
source has more carriers than target. For an example if there are 3 carriers in the source
cell and target cell has only 2, then nbrs will have to be duplicated . The first nbr will have
first common carrier and second will have second common carrier mentioned under
parameter NCHANNEL . Get the new nbr list defined.

DO_IFHO_2_to_1

(STA)Samsung Telecommunications America. All Rights Reserved. Confidential and Proprietary.

DO_IFHO_3_to_1 DO_IFHO_3-TO-2

Nbr audit process

The UNL should be run a day after migration for every migrated cluster to identify any missing nbr. Beyond that
The nbr list for every BSC needs to be audited once every month after migration. This duration can be higher or
lower based on frequency of migrations in the BSC
1) Post Migration nbr list modifications (addition/deletion/reprioritization) should be done based on CDL based
UNL and sector to sector HO stats. Tier 2 will provide CDL based analysis for requested days.
2) Every nbr present in 1900 layer (band class 1) should be in 800 layer too (Band class 0) except for non 800
sites.
3) Every SHO nbr should have reciprocity.
4) The outbound 1900 IVHHO nbrs and inound IVHHO nbrs should have reciprocity.
5) Every nbr relation having search set= 1 should have corresponding border carr definition

(STA)Samsung Telecommunications America. All Rights Reserved. Confidential and Proprietary.