100750495-E-naps-Process-v03

1/19 Document Type

Author

Unit/Dept.

Document Title

Date, VersionFor internal use

E-NAPS User Instructions

Simon Browne, Paresh Mahadik

V0.3 Jan 2009 (for E-NAPS version 1.6)

2/19 Document Type

Author

Unit/Dept.

Document Title


IntroductionThis document explains how to use the E-NAPS tool which has been developed primarily as an aid to the neighbour optimisation process. It can be useful particularly where NetAct Optimiser is not available to the project or where off-line working is required. It also contains functionality that can assist with crossed feeder analysis, which can be of benefit in swap/modernisation projects, for example.

The tool uses the NetAct Autodef HO statistics (tables M1013, M1014, M1015) as its data source to measure the 3G-3G and 3G-2G handover activity in the network, and, by referring this to the network neighbour databuild, produces an output file that is able to help with the identification of neighbours that can be added or deleted.

As E-NAPS uses the neighbour list combining functionality of NSN RAN, a basic neighbour plan needs remains a pre-requisite for an E-NAPS-based optimisation process.

Acknowledgement is due to John Wallace who produced the first ‘proper’ version of NAPS, which forms the basis of this tool. Because official development of NAPS was stopped the project is now continued within NPO (currently by Simon Browne), and this version is the result of a number of enhancements.

NAPS ProcessThe overall process uses two MS Access databases and a number of configuration and data files.

It will be found that the majority of the work in obtaining E-NAPS output is in the production of the miscellaneous build/configuration files. Running the tool itself is simply a case of selecting several MS Access macros.

Input FilesThis section describes the required input files. The figure below shows the relevant files and their relationships.

Three of the files are optional. NAPS_2G.xls and NAPS_3G.xls contain cell location and antenna azimuth information that is used to calculate the relevant inter-site distances and

3/19 Document Type

Author

Unit/Dept.

Document Title


provide the information that is used in the crossed-feeder analysis. File c_bts contains supplementary 2G cell information such as BCCH and BSIC info that can be useful in the final output. None of these are essential to the basic running of the tool.

File locations are specified in most cases – this is to simplify operation since a) E-NAPS uses linked database capability and b) a number of the macros use specified directories and filenames for the configuration files. The user who is familiar with MS Access can modify these if desired.

Each of the files is now considered in more detail.

1. Configuration Files

1.1 PE.mdb

Location: C:\USERS\Temp

This database contains the following tables,

1. A_ADJS: 3G-3G intra-frequency neighbour definitions2. A_ADJG: 3G-2G neighbour definitions 3. A_ADJI: 3G-3G inter-frequency neighbour definitions4. A_RNC: RNCs in the network5. A_WBTS: WBTS details6. A_WCEL: WCEL configuration

The database is typically the PlanEditor output mdb, normally obtained by exporting an xml file from CM Operations Manager on the OSS and processing this in PlanEditor. Once created the file should be renamed PE.mdb and placed in the location stated above.

4/19 Document Type

Author

Unit/Dept.

Document Title


It is advisable to restrict the mdb file to the RNCs of the area to be optimized (with their neighbouring RNCs if inter-RNC neighbour optimisation is to be done). This will speed up the overall processing time over having a file with the entire network!

In some cases, access to CM Operations Manager or PlanEditor may not be possible, and if general NetAct access is available then the required information can be obtained by running a set of sql scripts on the database. The output files can then be imported into an empty PE.mdb and this becomes the network build reference. See Annex 1 for the relevant scripts and the empty database.

1.2 NAPS_2G.xls


This is an excel file containing the 2G cell location information in the network. The format is as in the table below and the data in the attached file can be modified accordingly (note that column headings must be as in the file). EASTING and NORTHING values are in metres.

CELL_ID LAC EASTING NORTHING AZIMUTH12345 23456 501392 204701 19022346 23456 501392 204701 80

C:\USERS\3G\Tools\ENAPS\NAPS_2G.xls

1.3 NAPS_3G.xls


This is an excel file containing the 3G cell location information in the network. The format is as in the table below and the data in the attached file can be modified accordingly (note that column headings must be as in the file). EASTING and NORTHING values are in metres.

CELL_ID RNC_ID EASTING NORTHING AZIMUTH11000 55 532711 181083 021000 55 532711 181083 120

C:\USERS\3G\Tools\ENAPS\NAPS_3G.xls

5/19 Document Type

Author

Unit/Dept.

Document Title


1.4 c_bts.csv


This file contains additional cell information for the 2G cells, such as BSC and BTS names, BCCH frequency and BSIC info. The data can be extracted from NetAct with the attached SQL script and the file should then be placed in the above location. Example data is shown below.

BSC_NAME,BTS_NAME,CELL_ID,2G_LAC,NCC,BCC,MS_TX_PWR_MAX_CCH,BCCH

BSC123,07409#Old_Trafford,7409,1000,5,6,5,53

BSC123,07410#Moss_Rose,7410,1000,1,1,5,55

The example csv in Excel is here:

C:\USERS\3G\Tools\ENAPS\c_bts.csv

The SQL script for NetAct that extracts this is below:

C:\USERS\3G\Tools\ENAPS\2g_bts_naps.sql

1.5.NAPS_Config.xls


This excel file defines the RNC(s) for which output is required, the start and end dates for the period over which the data is to be analysed (can be a subset of the whole dataset), and the neighbour addition thresholds to be used.

Note that the RNC Name field is the RNCName value as found in the PE table A_RNC. The start and end dates are inclusive and are in format yyyymmdd.

The AddShare and AddHOs fields are used in the calculation of whether an undefined neighbour should be considered for addition. It will be shown in the final output files as a required addition (Status = ‘New’) if the HO Share in the output is >= xxAddShare AND the number of handovers is >= xxAddHOs in either the outgoing or incoming HO paths (SHO), or on the outgoing path only (ISHO, IFHO).

AddShare values are expressed as the HO Share % / 100, i.e. 0.015 represents 1.5% HO Share (see output file description for definition). The default values in the table below would result in a neighbour being recommended for addition if a HO Share >= 1.5% is found for an undefined neighbour with at least 5 handover attempts in the defined period.

3G3GAddShare/3G3GAddHOs are used for intra-frequency handover (SHO), 3G2GAddShare/3G2GAddHOs are used for ISHO and IFAddShare/IFAddHOs are for IFHO.

6/19 Document Type

Author

Unit/Dept.

Document Title


RN

C N

ame

Sta

rt D

ate

End

Dat

e

3G3G

Add

Sha

re

3G3G

Add

HO

s

3G2G

Add

Sha

re

3G2G

Add

HO

s

IFA

ddS

hare

IFA

ddH

Os

ABC-123 20081210 20090130 0.015 5 0.015 5 0.015 5ABC-234 20081210 20090130 0.015 5 0.015 5 0.015 5

An excel file that can be modified is below.

C:\USERS\3G\Tools\ENAPS\NAPS_Config.xls

7/19 Document Type

Author

Unit/Dept.

Document Title


2. Handover Statistics Files

2.1. SHO.csv


This file contains the SHO statistics. The format of data is comma separated, as below, and in the attached excel:

PERIOD_START_TIME,S_RNC,CID_ID,T_RNC,TCID_ID,SHO_ADJ_INTRA_FREQ_SHO_ATT,SHO_ADJ_INTRA_FREQ_SHO_COMPL

20090106,RNC1,11026,RNC1,11192,2501,2461

20090106,RNC1,11026,RNC2,11213,16,16

C:\USERS\3G\Tools\ENAPS\SHO.csv

The data can be generated by the below sql script:

C:\USERS\3G\Tools\ENAPS\autosho_NAPS.sql

This should be run from the SQL prompt on NetAct as, for example:

@autosho_NAPS.sql 2009010700 2008010823

The two arguments provided represent the start and end times, respectively, in format yyyymmddhh. The data is aggregated by the script into daily totals in the output file. The output file should be stored locally in C:\Users\Temp as SHO.txt.

If the data is produced in another way then the column headers should be made as shown in the above example and the date/time format for the PERIOD_START_TIME field should be yyyymmdd to align with NAPS_config.xls. Also the S_RNC and T_RNC fields must be the same as RNCName in A_RNC in PE.mdb.

An example csv file is here:

2.2. ISHO.csv


8/19 Document Type

Author

Unit/Dept.

Document Title


This file contains the ISHO statistics. The format of data is comma separated, as below, and in the attached excel:

PERIOD_START_TIME,RNC,CID_ID,LAC_ID,CI_ID,HO_ADJ_INTER_SYS_HHO_ATT,HO_ADJ_INTER_SYS_HHO_COMPL

20090106,RNC1,11020,14245,13668,2,2

20090106,RNC1,11020,14245,20272,1,1

C:\USERS\3G\Tools\ENAPS\ISHO.csv


C:\USERS\3G\Tools\ENAPS\autoisho_NAPS.sql


@autoisho_NAPS.sql 2009010700 2008010823

The two arguments provided represent the start and end times, respectively, in format yyyymmddhh. The data is aggregated into daily totals in the output file. The output file should be stored locally in C:\Users\Temp as ISHO.csv.

Similar formatting rules apply as to SHO.csv, but in this case ‘RNC’ is RNCName in A_RNC.

2.3. IFHO.csv


This file contains the IFHO statistics. The format of data is comma separated, as below, and in the attached excel:

PERIOD_START_TIME,S_RNC,CID_ID,T_RNC,TCID_ID,HHO_ADJ_INTER_FREQ_HHO_ATT,HHO_ADJ_INTER_FREQ_HHO_COMPL

20090106,RNC1,16031,RNC1,11031,656,656

20090106,RNC2,16031,RNC2,13371,39,38

9/19 Document Type

Author

Unit/Dept.

Document Title


C:\USERS\3G\Tools\ENAPS\IFHO.csv


C:\USERS\3G\Tools\ENAPS\autoifho_NAPS.sql


@autoifho_NAPS.sql 2009010700 2008010823

The two arguments provided represent the start and end times, respectively, in format yyyymmddhh. The data is aggregated into daily totals in the output file. The output file should be stored locally in C:\Users\Temp as IFHO.csv.

The same formatting rules apply as to SHO.csv.

Alternative SQL

An alternative to running each of the above three sql scripts individually is to use the below ‘master’ script (naps_stats.sql) which calls each of the three scripts individually (and located in the same NetAct directory) with the given date/time arguments and is run as:

@naps_stats.sql 2009010700 2008010823

It will generate three files, which, when run as above will be:

2009010700-2009010823SHO.txt

2009010700-2009010823ISHO.txt

2009010700-2009010823IFHO.txt

As stated above, these should be renamed accordingly and placed in C:\Users\Temp.

C:\USERS\3G\Tools\ENAPS\naps_stats.sql

10/19 Document Type

Author

Unit/Dept.

Document Title


2. E-NAPS Database and the Analysis Process

2.1.E_NAPS_1_6.mdb

Location: Not specific.

C:\USERS\3G\Tools\ENAPS\E_NAPS_1_6.zip

This database is the main processing engine. It is linked with PE.mdb to access the network build information in the network, and macros import the relevant configuration files and statistics and export the final analysis.

To use the full functionality the macros should be run in the following order:

1. CLEAR ALL TABLEs2. E IMPORT 2G CELL DATA3. E IMPORT 3G CELL DATA4. E IMPORT C_BTS5. E IMPORT SHO6. E IMPORT ISHO7. E IMPORT IFHO8. E ANALYSE

The functionality of the above is as below, with numbering corresponding to the steps above:

11/19 Document Type

Author

Unit/Dept.

Document Title


1. Ensure database is clean2. Import NAPS_2G.xls (C:\Users\Temp\NAPS_2G.xls)3. Import NAPS_3G.xls (C:\Users\Temp\NAPS_3G.xls)4. Import c_bts (C:\Users\Temp\c_bts.csv)5. Import SHO stats (C:\Users\Temp\SHO.txt)6. Import ISHO stats (C:\Users\Temp\ISHO.txt)7. Import IFHO stats (C:\Users\Temp\IFHO.txt)8. Analyse data and produce output file.

Note that 2-4 are optional but do provide useful information, and 2-3 are critical for any crossed feeder analysis. Any of 5-7 can also be excluded if not relevant, e.g. if only wanting to perform intra-frequency SHO analysis then only 6 needs to be run.

The output file produced is C:\Users\NAPS_Out.xls. Ensure that there is no existing version of NAPS_Out.xls in C:\Users before running the E-NAPS macros, or the output will fail.

Since Excel is used as the output file type a restriction of 65536 rows applies. This may be reached if multiple RNCs are listed in NAPS_config.xls. It is therefore recommended that the file output is checked if multiple RNCs are to be analysed and if the size limit is reached in any sheet (most likely to be SHO) then E-NAPS is run several times, changing NAPS_config.xls each time to reduce the number of RNCs analysed each time. In this case, rather than running macro ‘CLEAR ALL TABLEs’ as step 1 the macro ‘CLEAR ALL TABLES EXCEPT SHO ISHO IFHO’ can be used on the subsequent runs and this will leave the HO statistics data in the database – so steps 5, 6 and 7 can be skipped.

Using a Lenovo T61p machine with dual core processor and 3GB RAM, 2 RNCs were analysed for central London in 6 minutes with a manually-created (from sql) PE.mdb containing the whole cluster of 15 RNCs. By using a PE.mdb with only 5 RNCs (the two RNCs of concern and their neighbours) the run time was reduced to ~3 minutes. On less powerful machines the run time can be expected to be longer.

12/19 Document Type

Author

Unit/Dept.

Document Title


3. OUTPUT

3.1. NAPS_OUT.xls

Location: C:\USERS

File NAPS_Out.xls contains the full analysis.

It contains 7 sheets;

1. ISHO 2. SHO3. IFHO4. ACF5. ADJG6. ADJI7. ADJS

The content of these is now explained.

13/19 Document Type

Author

Unit/Dept.

Document Title


1. ISHO

The ISHO sheet provides information about inter-system handover activity from the 3G cells in the RNC(s) defined in NAPS_config.xls. The total handover attempts and successes are shown per adjacency pair (whether defined or not) which can be used in decision making regarding ADJG deletion and addition.

The following table explains each column.

Column Heading ExplanationRncId Source 3G RNC IDLAC Source Location Area CodeWBTSId Source WBTS IDWBTSName Source WBTS NameLcrId Source LCR IDCId Source Cell IDAdjgLAC Target 2G Location Area CodeAdjgCI Target 2G Cell IDBSC_NAME Target 2G BSC ID *BTS_NAME Target 2G BTS name *Distance Distance between source and target (m)MaxActDistance Distance to furthest used target cell MaxDefDistance Distance to furthest defined target cellHOs Number of handovers attempts between source and target cellHOsTotal Total number of outgoing ISHO attempts from source cellHOsShare Handover share with target (i.e. HOs/HOsTotal)Success_Rate Success rate of handoverDefined "Yes" if neighbour is defined or "No" if notAdjgCount Total number of defined 3G-2G neighbours for source cellAdjsCount Total number of defined 3G-3G intra-frequency neighbours for sourceAdjiCount Total number of defined3G-3G inter-frequency neighbours for sourceAdjTotal Total number of defined Adjg, Adji and Adjs neighbours for source2G_Incoming_HOs Total number of incoming handovers for the target 2G cell2G_Incoming_SUs Total number of successful incoming handovers for target 2G cellNCC Target NCC*BCC Target BCC*BCCH Target BCCH*

Status“Existing” if defined or “New” if HO activity exceeds both thresholds set in NAPS_Config.xls

ADJGId ADJGId of defined neighbour

Modified_Adjg_countTotal number of 3G-2G neighbour including suggested new neighbours.

* These fields will be blank if the target cell is not in table c_bts

14/19 Document Type

Author

Unit/Dept.

Document Title


2. SHO

The SHO sheet provides information about intra-frequency handover activity. The table displays all handover activity to/from cells on RNCs listed in NAPS_config.xls plus any cell on neighbouring RNCs for which statistics/ADJS definitions are available that have activity to/from the RNC(s) in NAPS_config.xls. The reason for providing output for the latter group of cells is to allow inter-RNC handover optimisation to be performed, whether or not the neighbouring RNC(s) are defined in NAPS_config.xls.

Column Heading ExplanationRncId Source 3G RNC IDWBTSId Source WBTS IDWBTSName Source WBTS NameLcrId Source LCRIDCId Source Cell IDAdjsRNCid Target RNC IDAdjsWBTSId Target BTS IDAdjsWBTSName Target BTS nameAdjsLcrId Target Lcrid IDAdjsCI Target Cell IDDistance Distance between source and target (m)MaxActDistance Distance to furthest used target cell (m)MaxDefDistance Distance to furthest defined target cell (m)HOs Number of handovers attempts between source and target cellHOsTotal Total number of outgoing SHO attempts from source cellHOsShare Handover share with target (i.e. HOs/HOsTotal)Success_Rate Success rate of handoverDefined "Yes" if neighbour define or "No" if notAdjgCount Total number of defined 3G-2G neighbours for source cellAdjsCount Total number of defined 3G-3G intra-frequency neighbours for sourceAdjiCount Total number of defined 3G-3G inter-frequency neighbours for sourceAdjTotal Total number of defined Adjg, Adji and Adjs neighbours for sourceBiMonitored Yes if target cell RNC statistics are availableBiHOs Number of SHO attempts in return path (from target to source cell)BiHOsTotal Total number of outgoing SHO attempts from target cellBiHOsShare Handover share of return path (BiHOs/BiHOsTotal)BiDefined "Yes" if return path is defined or "No" if not BiAdjgCount Total number of defined 3G-2G neighbours for target cellBiAdjsCount Total number of defined 3G-3G intra-frequency neighbours for target BiAdjiCount Total number of defined 3G-3G inter-frequency neighbours for target BiAdjTotal Total number of defined Adjg, Adji and Adjs neighbours for targetACF Adjacancy creation factor between source and target


ADJSId ADJSId of defined neighbour

Modified_Adjs_countTotal number of 3G-3G neighbour including suggested new neighbours.

Target PriScrCode Scrambling code of target cell

15/19 Document Type

Author

Unit/Dept.

Document Title


3. IFHO

The IFHO sheet provides information about intra-frequency handover activity. The table displays all handover activity to/from cells on RNCs listed in NAPS_config (i.e. the same logic is applied as for ISHO, rather than SHO, since the optimisation methods and rules for IFHO are generally different to those for SHO).

Column Heading ExplanationRncId Source 3G RNC IDWBTSId Source WBTS IDWBTSName Source WBTS NameLcrId Source LCRIDCId Source Cell IDAdjsRNCid Target RNC IDAdjsWBTSId Target BTS IDAdjsWBTSName Target BTS nameAdjsLcrId Target Lcrid IDAdjsCI Target Cell IDDistance Distance between source and target (m)MaxActDistance Distance to furthest used target cell (m)MaxDefDistance Distance to furthest defined target cell (m)HOs Number of IFHO attempts between source and target cellHOsTotal Total number of outgoing IFHO attempts from source cellHOsShare Handover share with target (i.e. HOs/HOsTotal)Success_Rate Success rate of handoverDefined "Yes" if neighbour define or "No" if notAdjgCount Total number of defined 3G-2G neighbours for source cellAdjsCount Total number of defined 3G-3G intra-frequency neighbours for sourceAdjiCount Total number of defined 3G-3G inter-frequency neighbours for sourceAdjTotal Total number of defined Adjg, Adji and Adjs neighbours for sourceBiMonitored Yes if target cell RNC statistics are availableBiHOs Number of SHO attempts in return path (from target to source cell)BiHOsTotal Total number of outgoing SHO attempts from target cellBiHOsShare Handover share of return path (BiHOs/BiHOsTotal)BiDefined "Yes" if return path is defined or "No" if not BiAdjgCount Total number of defined 3G-2G neighbours for target cellBiAdjsCount Total number of defined 3G-3G intra-frequency neighbours for target BiAdjiCount Total number of defined 3G-3G inter-frequency neighbours for target BiAdjTotal Total number of defined Adjg, Adji and Adjs neighbours for targetACF Adjacancy creation factor between source and target


ADJIId ADJSId of defined neighbour

Modified_Adji_countTotal number of inter-frequency neighbours including suggested new neighbours.

Target PriScrCode Scrambling code of target cell

16/19 Document Type

Author

Unit/Dept.

Document Title


4. ACF (Adjacency Creation Factor)

This sheet can be used for crossed feeder analysis.

The Adjacency Creation Factor (ACF) value is a measure of the alignment of the source and target cell antennas. If pointing towards each other the ACF value is 1. If pointing directly away from each other the value is 0. At 90 degrees offset the value is 0.5. All other alignments have corresponding intermediate values. There is no distance factor included in the E-NAPS calculations, unlike in Optimiser.

The following checks help in identifying crossed feeders.

1. Check column “Azi_Diff” If this is greater that 60 degrees it indicates 3G is handing over to co-located 2G sector >60 degrees offset and may have the wrong orientation. If more than one sector on a WBTS has an offset >60 degrees then this is particularly suspicious.

2. Check column “Avg_ACF” .If it is less than 0.7 check top 6 3G-3G target cells from NAPS out.xls, SHO sheet. Check orientation using MapInfo. Note that cells at the fringes of 3G coverage are likely to have low ACF and hence manual checking is always required.

The following table explains each field in the ACF sheet.

Column Heading ExplanationRncId RNC idWBTSId BTS IDLcrId LCR IDCId Cell IDAv_ACF Average ACF of non-co-located adjacencies having >=5% HO Sharecells Total number of non-co-located cells with >= 5% HO shareAdjsRNCid Target RNC ID for highest handover share cellAdjsWBTSId Target BTS ID for highest handover share cellAdjsLcrId Target LCRID for highest handover share cellAdjsCI Target cell ID for highest handover share cellDistance Distance between target cell with highest handover share and source cellHOsShare Handover share for highest handover share target cellMax_ACF ACF for source/target cell pairAv_Nbr_Distance Average distance of defined neighbours

Near_Nbr_Av_ACFAverage ACF for near neighbours (those at a distance less than the average defined distance)

ACF_Difference Delta between Av_ACF and Near_Nbr_Av_ACFAdjgCI Highest handover share co-located 2G cell ID 3G_Azi 3G cell azimuth2G_Azi 2G cell azimuth for highest handover share co-located 2G cell ID Azi_Diff Difference between 3G_Azi and 2G_Azi Summed_ACFs Summation of Max_ACF and Av_ACF

5-7 ADJG, ADJS and ADJI

17/19 Document Type

Author

Unit/Dept.

Document Title


Each of these sheets shows the defined adjacencies in the A_ADJG, A_ADJI and A_ADJS tables in PE.mdb. They may be useful if optimisation is to be performed to find free ADJ ids.

Column Heading ExplanationRncId RNC id of source cellWBTSId BTS ID of source cellLcrId LCR ID of source cellCId Cell ID of source cell0-31 Cell ID of target cell defined on ADJG/I/S ID 0 - 31

18/19 Document Type

Author

Unit/Dept.

Document Title


Annex 1 – Using Alternative PE.mdbIf a PlanEditor output database is not available then it is possible to use configuration data exported directly from NetAct using sql scripts. A version of PE.mdb is attached that has the tables created to take the sql output. There is also a macro to allow simplified data import. A zipped database is here:

C:\USERS\3G\Tools\ENAPS\PE.zip

The sql scripts to generate the required data files are in the attached zip file:

C:\USERS\3G\Tools\ENAPS\config_scripts.zip

They can be run together by using the ‘master’ sql script, naps_config.sql (below), if all the scripts are placed in the same NetAct folder. Note that naps_config.sql also runs the 2g_bts_naps.sql script attached earlier.

C:\USERS\3G\Tools\ENAPS\naps_configs.sql

The output of all the scripts, i.e. adjg.csv, adji.csv, adjs.csv, rnc.csv, wbts.csv and wcel.csv should then be placed into C:Users\Temp locally to allow macro import to work.

To run the macro import in PE.mdb simply run macro ‘IMPORT FILES’. (To ensure that the database is clean first the macro ‘DELETE FILES’ can be run ) This will automatically import the required files from C:\Users\Temp, assuming they are in the correct format and are named correctly.

The scripts do not currently have any means of filtering the RNCs for which the build information is gathered. If the entire OSS cluster is large then it will slow down the E-NAPS processing time, and if it becomes excessively slow then there will be a benefit to manually filtering the data in the csvs to the RNCs of concern together with their neighbours.

19/19 Document Type

Author

Unit/Dept.

Document Title


Annex 2: Outputting to 3GNetPlan.mbx for Crossed Feeder AnalysisThis section explains how to use 3GNetPlan MapInfo utility to assist crossed feeder identification.

3GNetPlan was produced by Rittavee Chantarakul and is an excellent and quick way of visualizing neighbour definitions in MapInfo. Follow Rittavee’s instructions in the guide within ‘Readme.zip’ below for general usage of the mbx first.

The following process gives a brief explanation of how it can be used to assist with crossed feeder detection.

1. Save NetPlan.mdb under C:\Users\Temp 2. “A_RNC” and “A_WCEL” will be linked to PE_mdb..3. A_ADJS will get imported when the user runs “Export ACF NetPlan” from

E_NAPS_1_6.mdb and should be blank before that macro is run (if it is not blank then it can be cleared by running macro ‘DEL ADJS’ in NetPlan.mdb).

4. Open MapInfo5. Select “Run MapBasic Program”6. Select “3GNetPlan.mbx”7. 3GNetPlan menu will appear on MapInfo menu bar8. Create new cellinfo.tab for network ( used attached instruction in Readme)9. Open Netpaln.mdb using open database under menu 3GNetPlan10. Select “find adj by SC” enter source cell scrambling code under investigation, enter

RNC id and if there are duplicate SCs select the correct cell ID.11. Target cells with HO share greater than 5% will be highlighted in blue. This will aid the

visual inspection of handover usage from the source cell and help identify any incorrect Tx feeder implementation.

3GNetplan200.zip

C:\USERS\Temp\NetPlan.zip

Readme.zip

100750495-E-naps-Process-v03

Documents

Transcript of 100750495-E-naps-Process-v03