Neighbour cell Management

Version:

1.4

Date:

25 Jan 2007

Author:

Sibabrata Majumdar

Department:

RO - QOS Optimisation

Filed As:

{File

Status:

Draft

Approved:
Signature / Date:

Neighbour cell Management

Version: 1.4

................................................... /...................

25 Jan 2007

Page 1 of 42

Document History
Version

Date

Reason

26-10-05

New Document

1.2

31-10-05

More detail on creating GPEH

trace

1.3

24-05-06

Ncell Management Process

1.4

25-01-07

Update to include information

on NCS-G and new database
for Ncell deletions.

1.1

Document Distribution
RO - QoS Optimisation

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 2 of 42

EXECUTIVE SUMMARY

This document is intended to explain the best practice Neighbour Cell Management
process to plan the 3G and 2G network. This document is intented to limit the analyse
work required for Ncell Management and to try to automate the addition and removal
process as much as possible.
Due to on-going rollout and constant increase and change of traffic profile on 3G the Ncell
management process will occur on a more regular basis. The MSA details the Ncell
Management process whould occur on all BSC/RNCs atleast every 6 months.
Current in-Scope
The scope of this documents covers the management process for 3G - 3G intra and IRAT
neighbours and 2G-2G neighbours. The document and is based on currently available
tools.

GCELL

TEMs Investigation

Atoll

Business Objects.

GPEH

NCS Planner

VISA / GPD

NCS-G (Not yet available for BAU)

Current Out of scope

This document does not cover future tools which have yet to be deployed. These include
but are not limited to,

NCS-W

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 3 of 42

TABLE OF CONTENTS
1

INTRODUCTION........................................................................................................... 5

3G OVERALL NCELL MANAGEMENT PROCESS........................................................6

3
3.1
3.2
3.3

3g Neighbour cell deletion process................................................................................7

Interim Neighbour Cell deletion process........................................................................7
Ideal/Final Intra 3G-3G deletion process:.......................................................................7
IRAT Handover deletion process:...................................................................................7

4
4.1
4.2
4.3

3G Neighbour cell addition process...............................................................................8

Interim 3G-3G Neighbour cell addition...........................................................................8
Final 3G-3G Neighbour cell addition..............................................................................8
IRAT Neighbour cell addition process............................................................................8

5
5.1
5.2

2G OVERALL NCELL MANAGEMENT PROCESS........................................................9

2G Neighbour cell deletion process.............................................................................10
2G Neighbour cell addition process.............................................................................10

A.1

Detail to 3G-3G Interim Neighbour Cell deletion process.............................................12

A.2

Detail to 3G-3G interim neighbour cell addition process..............................................28

A.3

Detail to 2G Ncell deletion process..............................................................................44

A.4

Detail to old 2G Ncell addition process........................................................................47

A.5

Detail to proposed new 2G-2G Neighbour cell addition process..................................49

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 4 of 42

INDEX

Report 1: Daily Cell performance

DAILY_CELL_PERFO
RMANCE_PA5.rep

.....................................................28

Figure 1: 3G-3G Neighbour Cell Management process....................................................................7

Figure 2: 2G Neighbour Cell Management process........................................................................10
Figure 3 Intra 3G-3G Ncell Deletion process..................................................................................13
Figure 4 Intra 3G-3G Ncell Addition Process..................................................................................29
Figure 5: 2g Neighbour Cell deletion process.................................................................................45
Figure 6: Neighbour cell process assuming NCS database is available.........................................48
Figure 7: 2g-2g Neighbour cell addition process using NCS-G......................................................50

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 5 of 42

INTRODUCTION

The document is intended to be used by the Regional Optimisation teams. The document
is a working document and will need to be updated as new tools and particularily counters
(3G-3G cell pair counters) are introduced to improve the Ncell management process.
The following section details the Neighbour cell addtion and deletion process the
engineers are to follow.

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 6 of 42

3G OVERALL NCELL MANAGEMENT PROCESS

Using the current tools, the procedure for 3G-3G Ncell addition and deletion is as follow:

Using statistics identify cells with

high missing neighbour drops

Use the network dumps to

identify cells with >=28 defined
3G-3G neighbours.

Use visual GIS and

measured data GPEH/TV to
identify missing neighbours or if
design changes are required.

Use GIS tool to identify

neighbours to remove and/or
agree design changes with the
CAT planner

Raise a CC to add the missing

neighbours or agree a design
change with the CAT planner

IMPORTANT: After changes

please monitor the performance
of the cell particularly Drops
due to missing Neighbour

Using statistics to measure

impact

3G-3G Ncell Addition Process

Interim 3G-3G Ncell Deletion Process

Figure 1: 3G-3G Neighbour Cell Management process

The OSS feature General Performance Event Handling (GPEH) is used to record events on the
network elements. The events are user defined. TEMS visualisation (TV)is used to post process
the output bin files from GPEH. TV produces an access database which can be used to export a
missing neighbour spreadsheet. Details as follows.

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 7 of 42

3G NEIGHBOUR CELL DELETION PROCESS

3.1

Interim Neighbour Cell deletion process

Until 3G-3G Intra cell handover counters are available the Ncell deletion process will be limited to
identifying cells with more than 28 defined neighbours and using GIS tools (Atoll or Mapinfo) to
identify the neighbours to delete. The detail to how to list the cells what meet the criteria for
deletion and to detail the tools and how to use them is detailed in Appendix Appendix A.

3.2

Ideal/Final Intra 3G-3G deletion process:

Once 3G-3G neighbour cell counters are activated, monitor the performance of the neighbour
cellpair relationships for the past 8 weeks. Look to delete any relationship not used. Once this
procedure is trailled a number of times the actully neighbour count and percentage count will be
defined.

3.3

IRAT Handover deletion process:

Counters on performance on 3G-2G performance was available until recently. Please run the
enclosed Business object report on the 3G-2G relationships for 1 month and remove any IRATs not
used. Note it is important to verify from the audits that the IRATs are not occurring due to
configuration errors.

IRAT_RNC_Cell_Lev
el-P3.rep

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 8 of 42

3G NEIGHBOUR CELL ADDITION PROCESS

4.1

Interim 3G-3G Neighbour cell addition

Currently the interim Neighbour cell addition process is to run GPEH on all RNCs. The GPEH files
are then post-processed using TEMS Visualisation (TV). Queries are added to the Access
database created by TV. All neighbour cellpairs that meet the query criteria are raised automatically
for neighbour addition.
The query qry_FindDistance is run and the cellpairs returned are raised for automatic neighbour
adds. The criteria the cellpairs need to meet are:
Distance <=5km (inside M25) <=12km (outside M25). The number of times the relationships must
appear as missing neighbours is set to >=30.
Note all cells that meet this criterion are raised for addition.
The detail to the process of running GPEH and post-processing with TEMS Visualisation is
detailed in Appendix Appendix B

4.2

Final 3G-3G Neighbour cell addition

Current NCS-W is being testing by TS. The proposed plan would be to run NCS-W and raise
neighbour additions that NCS-W recommends for addition. The latest documentation available for
NCS-W is located in teamrooms:

https://teamrooms1-vista.vodafone.com/eRoom/Global28/Radio/0_834ac

4.3

IRAT Neighbour cell addition process.

Currently IRAT neighbours are added using visual GIS tool e.g. Mapinfo or Atoll. The
process for addition is similar to the deletion process. Appendix Appendix Adetails on how
to use a mapinfo tool.
Until NCS-GW is available, the IRAT Ncell addition process will be limited to identifying
cells with less than 5 defined neighbours and using GIS tool (Atooll or Mapinfo)to identify
the the 2G neighbours to define.
NCS-GW is currently being tested. NCS-GW is the strategic solution

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 9 of 42

2G OVERALL NCELL MANAGEMENT PROCESS

1. Audit neighbour related

parameters.

Run NCS-G on OSS

Using filters identify the

cells to add.

2. Use statistics to identify

cellpairs doing low number
of handovers

Raise a CC to add all the

neighbour cells
recommended by NCS-G

3. Raise a Clarify case to

delete the handovers

Monitor the performance

after addition.
4. Monitor performance
after deletion
2G neighbour cell deletion process

2G neighbour cell addition process

Figure 2: 2G Neighbour Cell Management process

As traffic profile is more stable in 2G than in 3G it is recommended Neighbour Cell Management to
occur on cells every 6 months. In 2G, the plan is to automate the neighbour cell management
process as much as possible with little analysis work required by the engineers. The data will
however be available for detailed analysis for the engineers.

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 10 of 42

5.1

2G Neighbour cell deletion process

For detail to the process please refer to Appendix Appendix C. Handover statistical data from GPD
is exported to a database. The query HO_Culler details a Max_Factor which is used to detail the
cellpairs to delete. The Max_Factor is a % maximum figure of the handover performance of the
cell. The formula below explains how it is calculated. The current value used to identify the cells to
delete is Max_Factor of 0.001 or 0.1%. The Max_Factor is defined as formula:

MAX FACTOR MAX HO12

; HO12 ; HO 21
; HO21
HO1
HI1
HO 2
HI1

Where:
HO12 = Handout cell 1 to cell 2
HO1 = Total handout from cell 1
HI2 = Total handin to cell 2
HI1 = Total handin to cell 1
HO21 = Handout cell 2 to cell 1
HO2 = Total handout from cell 2

5.2

2G Neighbour cell addition process

The Neighbour cell addition process assumes NCS-G has been handed over to BAU.
The current information on generating recording is located in:

https://teamrooms1-vista.vodafone.com/eRoom/Global28/Radio/0_834ac
The default parameters are set under the RNO/NCS parameter menu. These are currently set to:Relative Signal Strength = 4 dB
Multi Band Cell Off Cell = 7 dB
Absolute Signal Strength = -100dBm
No. Test Frequencies to be Added (Max) = 5
BA list change interval = 10 Mins
The plan is to add all the cells that meet this criterion. Recently running this on 5 BSC highlighted
300 cellpairs to add.
Appendix Appendix D details the old process which has not been available for the last 8 months
but has been included for reference.
The detail on the proposed new NCS-G process is in Appendix Appendix E.

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 11 of 42

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 12 of 42

APPENDIX A Detail to 3G-3G Interim Neighbour Cell deletion process

Start

Start mapinfo tool

Navigate to site
Delete Ncells as appropriate.

Check Ncells manually

Check Performance Counters

in BO report. In particular the
DCR for the cell and the drops
due to missing neighbour
counter
pmNoSysRelSpeechNeighbr

Delete Obvious Ncells,

Start Atoll 3G sessions

Navigate to site

Has cell
Filter on area on interest

Yes

Add Ncells back in.

performance
deteriorated?
No

Produce Coverage arrays

End

Check validity of existing

Ncells based on coverage
arrays

Figure 3 Intra 3G-3G Ncell Deletion process

Interim process Process:

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 13 of 42

Use the daily dumps to fillter on cells with more than 28 neighbours. Dumps are located in:

\\Rpd2\main\QoS_Optimisation_South\02.Technical_Team\11.O&M\04.RNC_dumps

open an Atoll session to predict the coverage of the sites.

ATOL N-Cell deletion

It is assumed that the reader has a basic working knowledge of Atoll.

Open a new Atoll session

To start a new 3G session select the file menu and then select Open from DB

Then from the file type drop down box select Oracle Database

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 14 of 42

Enter your Atoll username and Pwd and Enter the server as RPTDB

Select to open a 3G session.

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 15 of 42

Then select the site area regions you want to load. It is better to select only those areas youre
interested in rather then All the areas as this reduces the amount of data the Atoll session has to
deal with.

Once the session has finished loading you will need to import all the map data you require. You
can do this by selecting the Coffee cup Icon in the tool bar and selecting the required map data.
Having done this navigate to the site of interest. The simplest way of doing this is to type the site ID
into the Find site dialogue box near the top of the map window.

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 16 of 42

Once you have centred in on the site the zoom out so that you can view at least up to the 5 th Tier
Neighbours. You can then filter out all the other sites to speed up the array creation and general
navigation. To do this right click on the Sites folder in the Explorer Window (if the exporer window is
not present you can select it by going to the View Menu and selecting View Explorer Window) and
then Select Filter by polygon and draw a polygon around the sites and area youre interested in
studying.

You now need to run some predictions to see the coverage of each of the cells in the area. The
predictions folder in the Explorer window contains a list of the abvailable coverage arrays. You can
add further arrays by right clicking on the Predictions Folder and selecting New.

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 17 of 42

You will now be presented with the various available coverage arrays.
Select the desired Arrays (you can only select one at a time).

Right click on the Predictions folder and then select to Lock all the studies. This will prevent Atoll
from calculating arrays you are not interested in. Right click on each of the studies you want to
calculate and select to unlock the study. To run the studies right click on the Predictions folder and
select Calculate. If you get an error message saying the Predictions are missing the most likely
cause of this is that you havent loaded the Terrain map data.

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 18 of 42

The simplest way to work out which sectors should be Neighbours is to run a pilot dominance
Array. This was you can see where the dominance of one server borders another and you should
be able to then say that those cells are Neighbours. An example of this array is shown below.

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 19 of 42

Although this may appear to be a simple task you should be aware that cells which are not obvious
Neighbours visually may be the dominant server in any particular area. This is illustrated in the
figure below. Cell W3344101 is Circled in Red and has a relatively small immediate service area in
front of the transmitter. However it is the dominant server at the location of the mouse icon in the
screen shot some 5km away and across the service area of 3 other sites.

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 20 of 42

This means sector W3344101would need to be defined as a neighbour of sector W3337801 unless
the coverage was altered by downtilting the site. In this case it would be preferable to change the
coverage by downtilting the site, but if this is not possible then it would need to be added as a
neighbour. All tilt/orientation changes need to be agreed with the CAT planner.

There are other arrays which are available which may assist in deciding on Neighbours. These
include the Coverage by Transmitter array and the Overlapping Area array. The process for
generating them is the same as that described above.

The information attained from Atoll can then be used to delete or add Neighbours
A clarify case should be raised to get the required Ncells deleted.

Please ensure the performance of the cell where neighbours have been deleted is monitored, in
particular Drops due to missing neighbour and overall DCR. If the peformance degrades please
look to add the Ncells deleted.
Presently this will consist of checking the Business Objects report. An example report to run:

Report 1: Daily Cell performance

Neighbour cell Management

Version: 1.4

DAILY_CELL_PERFO
RMANCE_PA5.rep

25 Jan 2007

Page 21 of 42

PmNoSysRelSpeechNeighbr Number of drops due to missing Neighbours

PmNoSysRelSpeechSoHo Number of drops due to soft handover
There are many other counters included in this report but these are not within the scope of this
document.

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 22 of 42

APPENDIX B Detail to 3G-3G interim neighbour cell addition process

1. Identify Cell/Area/RNC for
analysis

Use statistics missing neighbour

drops to prioritise list.

2. Obvious

neighbours missing or
design issues
N

As traffic is low a 48 hr GPEH

recording period will ensure usable
data. As traffic grows, BHs for a 2
day window should be ok. Limit the
number of cells per RNC to 100 to
ensure no impact on processor load.

3. Run GPEH on cells missing

neighbour events.

4. Copy output bin files from

GPEH to network drive.

5. Latest TEMS

Generate TV .cel file as an

input to TV for processing

Visualisation cell file

Y
6. Run TV to create access
database.

Query criteria used to add missing

neighbours:
8. Run the query to identify the
missing neighbours

30 missing neighbour count

Distance <=12km for RNCs outside
M25, Distance <=5km for RNCs
inside M25.

10. Check Performance

9. Raise CC to add missing neighbours.

Figure 4 Intra 3G-3G Ncell Addition Process

The point numbering below refers to the flow diagram above Figure 4: Intra 3G-3G addition process.

Flow diagram Pt 1:

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 23 of 42

The plan is to do all the RNCs at least every 6 months. The BO script below can be used
to target the worst cells on the RNC. Please run the enclosed Business Object report, for
the previous working week (Mon-Fri) to identify the cells dropping due to missing
neighbours - counter pmNoSysRelSpeechNeighbr. The recommendation is for the
engineer to action on the cells having a total of missing neighbour drops for the week
greater or equal to 10

Mis s ing
Neighbour.rep

Export tab Table reason for drops from BO report. The file lists cells with decreasing
absolute missing neighbour drops. Columns have been added to the end to identify
engineer, fix, and progress of proposed solution as well as the current number of defined
neighbours. Statistics can help prioritise the list of cells. Absolute and % missing neighbour
drops is a recommended starting point. Overall DCR on the cells can also be taken into
account.

Flow diagram Pt 2.

Use Atoll to show the predicted coverage of the cell, identify any missing neighbours
and/or if the design can be improved. Section 3.1 on deletion of neighbours details more
information on Atoll
If missing neighbours have been identified, please raise a CC to add the missing
neighbours.

If design is an issue, Engineer is to agree tilt/orientation recommendations with the CAT

planner.

Flow Diagram Pt 3.

The events to record in GPEH for missing neighbour and handover are:

INTERNAL SOFT HANDOVER EVALUATION

INTERNAL SOFT HANDOVER EXECUTION
INTERNAL SOHO DS MISSING NEIGHBOUR
INTERNAL SOHO DS UNMONTORED NEIGHBOUR

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 24 of 42

It is recommended to limit the number of cells to 100 per RNC and run the data for 48
hours.

GPEH will be run on all the cells dropping greater than 9 drops due to missing neighbours.
The run will be started on every 2nd Monday the cells are identified and collected and
post-processed by COB Wednesday, ready for the engineers Thursday morning. The
following details the setting up of GPEH recording in OSS-RC.

The following instruction details the set-up of a GPEH profile in the OSS-RC:

a) From the OSS-RC explorer tool point the mouse on Performance and select
Initiate data collection- WCDMA RAN measurements. See the screen shot
below.

b) In the Data collection Subscription window tool bar select Administration-add

profile... This will give you Add GPEH/CTR/UTER Subscription wizard. Step 1 of
8 window. Here choose GPEH (Last profile in the list) and click next. See screen
shot below.

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 25 of 42

c) Step 2 of 8: Enter user name for profile and enter any additional information in the
bottom field (You can also ignore the bottom field) and press next. See the screenshot
below.

Note: Profile name is only used to differentiate your GPEH profile from other GPEH
profiles defined by other users in the GPEH profile window.

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 26 of 42

c) Step 3 of 8: Here select RNC network elements should be observed and click
next. See the screen shot below.

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 27 of 42

d) Step 4 of 8: Here select a RNC from the list of RNCs and click on the top arrow. By
doing this you will see that the RNC you have selected has moved from the left
pane to the right pane. Click next now.

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 28 of 42

e) Step 5 of 8: select the sites (100 sites per profile. If RNC has 200 sites please
define two separate profiles and stagger their activation by 30 min) and click next.

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 29 of 42

f) Step 6 of 8: Expand the GPEH_INTERNAL tree and choose the following events
in and move them across to selected events panes by clicking on the top arrow.
INTERNAL SOFT HANDOVER EVALUATION
INTERNAL SOFT HANDOVER EXECUTION
INTERNAL SOHO DS MISSING NEIGHBOUR
INTERNAL SOHO DS UNMONTORED NEIGHBOUR

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 30 of 42

g) Step 7 of 8. Leave UE fraction in 1000 and press next.

h) Step 8 of 8: This window will allow you to schedule this GPEH profile to run. Once
you have scheduled it press Finish to complete the GPEH set up.

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 31 of 42

Now you have defined a GPEH profile and this GPEH profile can be found in Data
collection Subscription profile window under GPEH profile tap. You modify the profile by
selecting your profile and right click on it.

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 32 of 42

Flow diagram Pt 4

Copy the data from OSS-RC server to a network or local drive.

GPEH trace files can be found in the following directory on ssranos02 server:
/var/opt/ericsson/nms_umts_pms_seg/segment1/SubNetwork=RNCKS1/MeContext=RNC
KS1.

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 33 of 42

The above path is only corresponds to the location of GPEH traces for KS1. So please
change the RNC name accordingly for other RNCs.

To fetch the data from the ssranos server your need to FTP into the server then fetch from the location of trace files.

Flow Diagram Pt 5:

Latest TV cell file is located in:

\\Ntfiler1\dl_to_south_qos\TEMS Visualisation.

The cell file is required to ensure the correct cell and RNC is identified with the measured
SC.

Flow diagram Pt 6

Run TEMS Visualisation

Open TV

File Import Import WCDMA files. Browse for the TV cell file , select the
correct timezone and the tick box available. See figure below

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 34 of 42

In the next screen select Select Folder and point to where the bin files to be
processed are located as below.

In the next screen select all the options see below. Ensure the missing
neighbour guard time is set to 5 sec. Note as we are recording only missing
neighbour events, the dropped calls, pilot pollution, blocked calls will all be
blank. Click Start. This process can take up to 40 mins depending on how
many cells and how busy the cells are.

Flow diagram Pt 7: The database created will be in location:

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 35 of 42

\\rpd2\main\QoS_Optimisation_South\02.Technical_Team\11.O&M\05.GPEH\Sib
The query qry_FindDistance is run and the cell pairs returned are raised for automatic
neighbour adds. The criteria the cell pairs need to meet are:
Distance <=5 (inside M25) <=12 (SEMS or outside M25). The number of times the
relationships must appear as missing neighbours is set to >=30.
Note all cells that meet this criterion are raised for addition using the NCell Management
process.
Flow Diagram Pt 8:

DP will raise the CC to add the missing neighbours after the SC clashes and maximum
neighbour cells have been checked.
To support the on-going optimisation process the raw data will be available for the
engineer to change the distance and missing neighbour count criteria. The data can be
used to support tilt requests. The database is created below. It is recommended the
engineers copy this to his local drive.
Flow Diagram Pt 9:
Check the performance of the cell after the neighbour additions have been implemented
using statistics. Please refer to Business Object report Daily Cell on link Report 1.

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 36 of 42

APPENDIX C Detail to 2G Ncell deletion process

1. Identify BSC to delete

neighbours on.

The engineer should target all

BSCs they look after.

2. Ensure handover related

audit is complete.

Either use VISA queries or

consistency checks from CNA to
identify audit issues.

3. Raise a CC request to fix

the audit issues

4. Wait two weeks after

audits have been corrected
or exclude the cells from
the deletion plan.

5. Run database

Run data for a 6 week period.

6. Raise CC to remove low

performing neighbours.
Change the activity factor
as required

7 IMPORTANT: Review the

performance of the cells/Area after
implementation of deletions..

Figure 5: 2g Neighbour Cell deletion process

The enclosed refers to the points from the flow diagram above: Figure 5.
Flow diagram Pt1:
It is recommended the engineers look to run a deletion plan on all the BSCs they look after on a 6month window.

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 37 of 42

Flow diagram pt2:

Certain configuration audits need to be done that relate directly to handover. The most important
ones that will after the performance between cellpairs are:

Measurement channel check. (VISA script available GSM BALIST CHECK

Co-Channel Co-BSIC CO-CHANNEL CO-BSIC

Co-Channel Co-BCCH CO-CHANNEL CO-BCCH

1-way neighbours (CNA can be used0

Incorrect ext Definitions on BSCs. (CNA can be used)

Incorrect MSC data (MGCEP and MGOCP) VISA

Except for Co-channel co-bsic any inconsistencies above will lead to no handover data between
the cellpairs. Co-channel co-bsic error will cause poor handover performance.
Flow diagram pt3.
To fix the audits for most of the configuration errors are easy:

Measurement channel check. (VISA script available GSM BALIST CHECK

1-way neighbours (CNA can be used0

Incorrect ext Definitions on BSCs. (CNA can be used)

Incorrect MSC data (MGCEP and MGOCP) VISA

To fix co-channel co-bsic errors will require a new BSIC plan. To fix the co-channel co-bcch will
require a new bcch plan.
Flow diagram pt4.
To ensure we have statistical data to work on it is recommended to have 4 weeks of data available
after the configuration errors highlighted in P2 are completed. The option is not to include these
cells in the removal process.
Flow diagram pt5.
Open database.

\\rpd2\main\QoS_Optimisation_South\10.Tools\34.Autoplanner\HOEvaluator_v1.mdb
Run macro Build. The macro is currently set to record handover data for 60 days.
The query HO_Culler has filter based on Max_Factor to select the least active relations. The factor
used depends on the level of aggression required for the cull. A good starting point is to consider
removing all relations with a factor of less than 0.1% (i.e. set to 0.001)
The table HO2Cull is the neighbour cells to delete.
Flow diagram pt6.

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 38 of 42

Raise a record job to delete the neighbours that meet the criteria in Pt 5.
Flow diagram pt7.
It is extremely important for the engineer to monitor the performance of the BSC and cell level after
the deletions. The KPIs to monitor are DCR and reasons of the drops. VISA scripts available: GSM
TCH CELL and GSM TCH DROP CELL. It is recommended to check the BSC and cell level
performance at least 48 hours after the deletions.

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 39 of 42

APPENDIX D Detail to old 2G Ncell addition process

1. Identify BSC to add
neighbours

The engineer should target all

BSCs they look after every 3
months

2. Run BAR/NCS recording

and collect the data.

Either use VISA queries or

consistency checks from CAN to
identify audit issues.

3. Analysis

manual

3a. Use the NCS data to

investigate specific site issues
e.g. poor performance/ crossed
feeders.

automatic
3b. Run the query to
identify neighbours to add

The query value to use is location

dependant..

4. Raise CC to add all

missing neighbours
identified by the tool..

5. Review the performance

of the cells/Area after
implementation of additions.
Figure 6: Neighbour cell process assuming NCS database is available.
This process is assuming we have NCS data to analyse. All the BSCs are now R12. A parser will
be required to process the NCS recording. We have not had NCS data since March 2006.
Flow diagram pt1
The engineer should look to run NCS on all the cells on the BSCs they look after on a 3-month
period.
Flow diagram pt 2.
Please run NCS on all the cells. The commands to set up a record and to retrieve the files are
detailed in the enclosed excel sheet. The optimisation team can decide whether this task should be

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 40 of 42

done centrally or by the engineer looking after the BSCs. Within a short period GPD should be
populated with the recording results

ncs cmd file.xls

Flow diagram pt3.

The processed data can be viewed through Access. The data is located in:
\\rpd2\main\QoS_Optimisation_South\10.Tools\04.2G_Optimization\01.2G_Integrations\2GNcellManagement
.mdb
Please copy the tool onto your PC

Flow diagram pt3a.

The engineer will have the data available for detailed analyse. The data is extremely useful to
identify over-propagating sites and crossed-feeder issues. The engineer, with the support of the
CAT planners and CFF engineers can process a course to improve the design of the site. The
detailed analysis is outside the scope of this document. The explanation is covered in the best
practice optimisation document.
Flow diagram pt3b.
Run the query NcellAdd in the access database above. The additions are based on the %sample
times the missing neighbour appears in the recoding results and the distance of the undefined
neighbours. The filter is set to %sample=4% and distance <=10km. The filter can be modified
depending of the environment, urban, rural etc. It is recommended the engineer do a sanity check
of the additions being proposed.

Flow diagram pt4

Please raise a Clarify Case requesting the additions.
Flow diagram pt 5.
After implementation, please review the performance of the cell. The best scripts to run are:
GSM_TCH_CELL, which will detail the main KPIs DCR, MHT, and Erlang Minutes per Drop. The
engineer can also run ERIC_HANDOVER_CELLPAIR to detail the handover performance of the
newly defined neighbours. Note that the configuration changed detailed in the deletion process can
also be run to ensure the new neighbours
haveonbeen
Run NCS-G
OSSdefined correctly on the BSCs.

APPENDIX E Detail to proposed new 2G-2G Neighbour cell addition

process

Using filters identify the

cells to add.

Raise a CC to add all the

neighbour cells
recommended by NCS-G

Neighbour cell Management

Version: 1.4

Jan 2007
Monitor the25performance
after addition.

Page 41 of 42

Figure 7: 2g-2g Neighbour cell addition process using NCS-G

Note the NCS-G process is yet to be handed over to BAU. The current information on generating
recording is located in:

https://teamrooms1-vista.vodafone.com/eRoom/Global28/Radio/0_834ac
The default parameters are set under the RNO/NCS parameter menu. These are currently set to:Relative Signal Strength = 4 dB
Multi Band Cell Off Cell = 7 dB
Absolute Signal Strength = -100dBm
No.Test Frequencies to be Added (Max) = 5
BA list change interval = 10 Mins
The plan is to add all the cells that meet this criterion.

Neighbour cell Management

Version: 1.4

25 Jan 2007

Page 42 of 42